IBM Netezza Performance Server is a good tool. The solution's performance is not that great compared to Oracle Exadata. If you don't have much money to spend on Oracle Exadata, you can always go ahead with IBM Netezza Performance Server. It will help you complete your work.

We were previously using Oracle Database. We switched for performance reasons and running complex queries. Compared to Oracle, Netezza has superior performance.

Our previous solution was in Oracle which had a custom data model. The reason for the change in technology was due to the data model. The new data model was purchased from IBM and their recommendation was to use Netezza for it.

Previously, Oracle was used as the data warehousing platform, and performance was low and not meeting the needs of the enterprise reporting and analytic user community. My customer switched to Netezza mainly for performance, and it was a big improvement.

1. Compared to other RDBMS, Netezza provides much higher performance and much lower maintenance effort
2. Compared to Teradata, lower cost and lower administration

We were saddled with this.

I used to have Oracle as my Data Warehouse solution, but despite the fact of it is very good to manage transactional environments, it does not work as fast as Netezza. We have analytical demands so we need an analytical solution. Sometimes we need to retrieve and process our whole table of inventory so it means around 16 billion of rows. Netezza can process all this amount of data and give a result in less than 40 seconds. I have never seen this performance in another database solution before.

I worked for different companies and my experience is really wide. Teradata is the paramount solution! Oracle’s Exadata invests a lot in both technology and marketing, sometimes losing the focus on “real” analytics. They used to address the platform as both OLAP and OLTP (“one size fits all”), which is not correct.

I have used Oracle and Teradata as a DBA. I have found Netezza to be the easiest in terms of DBA management

Netezza was the first one which we incorporated and started using heavily. Before that, we did test the other data warehousing technology but it was just a PoC and PoV test.

In some of our business areas, they still use SQL Server data warehouses and Oracle data warehouses. But once we moved to Netezza, different business units bought in, and now we are up to Hadoop solutions and AWS solutions.

We did not use a previous solution.

We previously used Oracle then migrated to Netezza because its deployment is easy, and there is less administration and coding when compared to Oracle. Also, the query performance is excellent in Netezza.

We had Teradata before, and I am not really sure why we switched.

Previously used DB2 LUW but this could not provide us with the performance we needed at the time. We looked at Netezza as they were trying to get a foothold in the UK and the portability of data and the speed with which it performed was incredible.

I've never used any other solutions.

We used other MPP architecture solutions such as Microsoft PDW and Teradata. However, Netezza has an edge as it is convenient to use and it doesn't need a database administrator to perform a successful implementation of a Netezza migration from any RDBMS.

No other solution was used previously.

The appliance is installed and maintained by vendor.

We're looking to switch away from Netezza because the platform database system that it runs on is no longer going to be in existence. It's moving to DB2. If it moves to that direction, the amount of changes in logic and queries that it would require is pretty substantial. At that point I would basically be rewriting everything.

When selecting a vendor, obviously I don't want somebody who is brand new. I want somebody who has a track record of actually being around for awhile. It needs to be a company with a product that does the functions that a database should do, and not something that's only a partial solution. There are a lot of solutions out there that do three-quarters of what a warehouse should be doing, but three-quarters of a warehouse are not sufficient.

Our IT leadership made the decision to go with Netezza before I joined the company, that decision had already been made. Prior to that we were using Microsoft SQL Server.

The only thing that I was really privy to was, Netezza was chosen because of its analytical capabilities and for the ability to process through a very high volume of records and give an aggregate solution from an analysis standpoint, in a very quick fashion.

We used Oracle previously. The performance required less maintenance when comparing index and data maintenance issues.

No previous solution was used.

It’s a complex setup.

We used Teradata for Data Mart for certain applications but issues arose once the data setup grew. Using PDA, the issues were resolved.

Non analytic databases used to be all there was. Netezza provides outstanding performance for structured data.