The cost of the solution is on the more expensive side, which is a concern for me. Additionally, its promotion and interaction with cloud applications are limited. The cloud version is only available in AWS, and in the Middle East, it is not well-developed in the Azure environment. For the cost to be reduced, it should match competitors. Many features need to be incorporated on the cloud.
Learn what your peers think about IBM Netezza Performance Server. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
Technical Lead at a financial services firm with 51-200 employees
Real User
2018-08-12T06:33:00Z
Aug 12, 2018
It really serves its purpose. It meets the need for performance, it meets the need for robustness, and it also serves as a perfect data warehousing appliance. The only issue is that it's not expandable. The new versions of Netezza, they are expandable. They can be on-prem and on the cloud like dashDB from IBM. It replaces the previous Netezza versions. We are currently on Mako because TwinFin support is going in 2019. Maybe in the next couple of years, we will be replacing Netezza with Redshift.
Business Intelligence Consultant at a tech services company with 51-200 employees
Consultant
2015-11-14T21:08:00Z
Nov 14, 2015
Concurrent Queries, with this model (1000-3), we had a very big problem using front-end tools connected on it. When using a dashboard tool to use data directly from the database, I had a big problem with queries being queued and stopped running. Looking at the manual I read that Netezza has a limited number or concurrent process.
IBM Netezza appliances are now part of IBM PureSystems - expert integrated systems with built in expertise, integration by design and a simplified user experience. Part of the PureData family, the Netezza appliance is now known as the PureData System for Analytics. It has the same key design tenets of simplicity, speed, scalability and analytics power that was fundamental to Netezza appliances.
The cost of the solution is on the more expensive side, which is a concern for me. Additionally, its promotion and interaction with cloud applications are limited. The cloud version is only available in AWS, and in the Middle East, it is not well-developed in the Azure environment. For the cost to be reduced, it should match competitors. Many features need to be incorporated on the cloud.
Oracle Exadata's security features, like TDE encryption, are missing in IBM Netezza Performance Server.
IBM Netezza Performance Server could improve its interface, support for big data, and APA-based connectivity should be available.
This is an appliance-based product with limited capability. It has all the horse-power that one can imagine and can handle all workloads.
They should make it work better in a multi-user context. This solution works, but not for the workload we have.
Our main problem with it is concurrency. When there are too many users running Netezza at the same time, this is when we have the most complaints.
It really serves its purpose. It meets the need for performance, it meets the need for robustness, and it also serves as a perfect data warehousing appliance. The only issue is that it's not expandable. The new versions of Netezza, they are expandable. They can be on-prem and on the cloud like dashDB from IBM. It replaces the previous Netezza versions. We are currently on Mako because TwinFin support is going in 2019. Maybe in the next couple of years, we will be replacing Netezza with Redshift.
Concurrent Queries, with this model (1000-3), we had a very big problem using front-end tools connected on it. When using a dashboard tool to use data directly from the database, I had a big problem with queries being queued and stopped running. Looking at the manual I read that Netezza has a limited number or concurrent process.