Smart Stuff
When upgrading your Netezza system to IBM® Netezza® Performance Server for Cloud Pak® for Data you will want to minimize system downtime. Read how Smart Management Frameworks' SmartSafe feature can reduce this to virtually zero.
By containerizing Smart Management Frameworks it allows us to bring our replication software to Netezza users on IBM's Cloud Pak for Data System.
The Log4j flaw, disclosed by Apache last week, allows attackers to execute code remotely on a target computer, meaning that they can steal data, install malware or take control. How can you tell if you have a problem on your Netezza host?
Netezza Performance Server version 11.2.2 now includes Replication Services. Although at first glance this sounds very similar to what our SmartSafe product also does, in fact there are many points of differentiation between the two offerings that customers should be aware of before deciding which is the best approach for them. Let’s explore some of these.
You don't have to invest in a secondary Netezza system that will remain idle to achieve a full disaster recovery solution - this can be achieved using SmartSafe multi-master bi-directional replication (BDR) which enables you to have a mean time to recovery (MTTR) and recovery point objective (RPO) measured in minutes whilst load balancing your users and maximising your ROI. Read more in our blog.
In this blog we'll show you how to massively reduce the runtime of Netezza queries on very large tables by up to 60 times.
IBM’s Netezza Performance Server systems are incredibly fault tolerant and are known to require far less effort to administer than a traditional RDBMS. This can, however, lead to a false sense of security, and so when DBA resourcing levels are reviewed, some businesses will attempt to reduce costs by handing over the day to day running of Netezza to a non-specialist team. But is this a good idea?
Fatal error: Cannot redeclare topperImage() (previously declared in /homepages/33/d146456827/htdocs/blog/index.php:2086) in /homepages/33/d146456827/htdocs/blog/index.php on line 3210