Netezza Performance Server (NPS) is an add-on data warehouse solution available on Cloud Pak for Data System platform, built over open source and optimized for High Performance Analytics with built-in hardware acceleration. Netezza Performance Server was previously named IBM Performance Server for PostgreSQL (IPS).
N/A
PostgreSQL
Score 8.7 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
N/A
Pricing
IBM Netezza Performance Server
PostgreSQL
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Netezza Performance Server
PostgreSQL
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Netezza Performance Server
PostgreSQL
Considered Both Products
IBM Netezza Performance Server
Verified User
Analyst
Chose IBM Netezza Performance Server
Netezza is sufficient against similar products. It comes down to personal preference, I'd love to have the data objects popping up as I type but some people may not like it.
We can query the data source and treat multiple databases as one with IBM Netezza Performance Server.
While delivering fast and reliable analytical performance, the IBM Netezza Performance Server requires minimal configuration and ongoing management.
To drive organizational performance, Netezza Performance Server automatically simplifies data and AI to centralize all analytics activities on the device, exactly where the data resides.
For data processing and application dashboards, IBM Netezza Performance Server is quite beneficial.
IBM Netezza Performance Server simplifies event setup by notifying you when a hardware component fails, allowing you to quickly replace it.
PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Netezza is sufficient against similar products. It comes down to personal preference, I'd love to have the data objects popping up as I type but some people may not like it.
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same family of applications that performs the company that develops it and that is not all bad, but being able to adapt or configure different programs, applications or other environments developed by third parties apart is what gives PostgreSQL a certain advantage and this diversification in the components that can be joined with it, is the reason why it is a great option to choose.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.