No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Netezza Performance Server vs Spark SQL comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 1, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Netezza Performance Server
Ranking in Hadoop
6th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
45
Ranking in other categories
Data Warehouse (11th)
Spark SQL
Ranking in Hadoop
5th
Average Rating
7.8
Reviews Sentiment
7.6
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Hadoop category, the mindshare of IBM Netezza Performance Server is 6.0%, up from 1.9% compared to the previous year. The mindshare of Spark SQL is 5.3%, down from 9.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Hadoop Mindshare Distribution
ProductMindshare (%)
Spark SQL5.3%
IBM Netezza Performance Server6.0%
Other88.7%
Hadoop
 

Featured Reviews

Shiv Subramaniam Koduvayur - PeerSpot reviewer
Project Manager at MAF Retail
Parallel data processing streamlines operations while cost and cloud integration challenge adoption
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.
Kemal Duman - PeerSpot reviewer
Team Lead, Data Engineering at Nesine.com
Data pipelines have run faster and support flexible batch and streaming transformations
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource management in Spark SQL should be better. It consumes more resources, which is normal. The main reason we switched from Spark is memory and CPU consumption. The major reason is the resource problem because the number of streaming jobs has been increasing in our company. That is why we considered resource management as a priority. Because of the resource consumption, I would say the development of Spark SQL is better. For development purposes, it is a top product and not difficult to work with, but resources are the major problem. We changed to Flink regardless of development time. Development time is less in Spark compared with Flink.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We have sub-second query performance, and users are happy with the product."
"ROI is high because analyst productivity improved drastically."
"Simplified development process with less administration."
"Netezza is an easy-to-use data warehouse appliance; it's extremely fast with a low cost and the customers run their BI and advanced analytics in a very flexible manner."
"It is a back end for our SSIS, MicroStrategy,, Tableau. All of these are connecting to get the data. To do so we are also using our analytics which is built on the data."
"The most valuable features of the IBM Netezza Performance Server are the NPS server because of the reduced maintenance and overall good performance."
"The ability to support a lot of complex queries to analyze rather big data sets at the same time is a valuable feature for us."
"It can run heavy CPU queries really fast, and this is valuable."
"Certain data sets that are very large are very difficult to process with Pandas and Python libraries. Spark SQL has helped us a lot with that."
"Spark SQL gives us a handful of methods to design queries based on its own syntax and also incorporates the regular SQL syntax within tasks."
"Overall the solution is excellent."
"Speed is the major benefit of using Spark SQL."
"Spark SQL's efficiency in managing distributed data and its simplicity in expressing complex operations make it an essential part of our data pipeline."
"Data validation and ease of use are the most valuable features."
"This solution is useful to leverage within a distributed ecosystem."
"The team members don't have to learn a new language and can implement complex tasks very easily using only SQL."
 

Cons

"Netezza has a single active host node that can become a performance bottleneck."
"IBM Netezza Performance Server could improve its interface, support for big data, and APA-based connectivity should be available."
"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."
"The hardware has a risk of failure. They need to improve this."
"Matching up with big data. Netezza has been built only for OLAP and structured data, and I think IBM must do something to match it to Hadoop scalability."
"Community support. There was none, or very little, especially when using add-on software (e.g. building functions, MapReduce, R, Lua, etc.)."
"In Aginity there should be a way to format the SQL queries."
"Integration with XML is still not there for nzload utility."
"I've experienced some incompatibilities when using the Delta Lake format."
"SparkUI could have more advanced versions of the performance and the queries and all."
"It would be useful if Spark SQL integrated with some data visualization tools."
"Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink."
"In the next update, we'd like to see better performance for small points of data. It is possible but there are better tools that are faster and cheaper."
"There are many inconsistencies in syntax for the different querying tasks like selecting columns and joining between two tables so I'd like to see a more consistent syntax."
"Anything to improve the GUI would be helpful."
"Being a new user, I am not able to find out how to partition it correctly. I probably need more information or knowledge. In other database solutions, you can easily optimize all partitions. I haven't found a quicker way to do that in Spark SQL. It would be good if you don't need a partition here, and the system automatically partitions in the best way. They can also provide more educational resources for new users."
 

Pricing and Cost Advice

"The solution has a yearly licensing fee, and users have to pay extra for support."
"Expensive to maintain compared to other solutions."
"For me, mainly, it reduces my costs. It's not only the appliance cost. There are also support costs and a maintenance costs. It does reduce the costs very drastically."
"The annual licensing fees are twenty-two percent of the product cost."
"Netezza is a costly solution. It does serve a specific purpose but it's costlier than what's available in the market, if you go to the cloud."
"The pricing is very expensive. It has a lot CPUs with a lot of components in it. It also has built-in redundancy for resiliency reasons."
"We use the open-source version, so we do not have direct support from Apache."
"The solution is bundled with Palantir Foundry at no extra charge."
"The solution is open-sourced and free."
"There is no license or subscription for this solution."
"The on-premise solution is quite expensive in terms of hardware, setting up the cluster, memory, hardware and resources. It depends on the use case, but in our case with a shared cluster which is quite large, it is quite expensive."
"We don't have to pay for licenses with this solution because we are working in a small market, and we rely on open-source because the budgets of projects are very small."
report
Use our free recommendation engine to learn which Hadoop solutions are best for your needs.
918,957 professionals have used our research since 2012.
 

Comparison Review

it_user232068 - PeerSpot reviewer
Senior Data Architect at a pharma/biotech company with 1,001-5,000 employees
Aug 5, 2015
Netezza vs. Teradata
Original published at https://www.linkedin.com/pulse/should-i-choose-net Two leading Massively Parallel Processing (MPP) architectures for Data Warehousing (DW) are IBM PureData System for Analytics (formerly Netezza) and Teradata. I thought talking about the similarities and differences…
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Outsourcing Company
15%
Manufacturing Company
10%
Comms Service Provider
10%
Financial Services Firm
15%
Comms Service Provider
11%
Manufacturing Company
10%
University
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise6
Large Enterprise33
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise6
Large Enterprise4
 

Questions from the Community

What needs improvement with IBM Netezza Performance Server?
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 availab...
What advice do you have for others considering IBM Netezza Performance Server?
The solution has generally received positive feedback from me and is recommended for continued use by end users. However, the product cost is high compared to others in the market, and this cost ha...
What needs improvement with Spark SQL?
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource manageme...
What is your primary use case for Spark SQL?
Spark SQL has been in our stack for less than one year, though some of our colleagues are using it. It is a useful product for transformation jobs. We generally use Spark SQL for batch processing. ...
What advice do you have for others considering Spark SQL?
Regarding the Catalyst query optimizer, I think we are using it. We were using it in the past, but I am not certain if we use it now. We used it a long time ago. I rate my experience with Spark SQL...
 

Also Known As

Netezza Performance Server, Netezza, Netezza Analytics
No data available
 

Overview

 

Sample Customers

Seattle Childrens Hospital, Carphone Warehouse, Vanderbilt University School of Medicine, Battelle, Start Today Co. Ltd., Kelley Blue Book, Trident Marketing, Elisa Corporation, Catalina Marketing, iBasis, Barnes & Noble, Qualcomm, MediaMath, Acxiom, iBasis, Foxwoods
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, Hitachi Solutions
Find out what your peers are saying about IBM Netezza Performance Server vs. Spark SQL and other solutions. Updated: September 2026.
918,957 professionals have used our research since 2012.