The solution's maintenance is quite easy. One person is enough to maintain the solution.

If you are using PostgreSQL as a database solution, then using IBM Netezza Performance Server is the logical choice since it is based on open-source Postgres. However, if you are using Oracle, data conversion can be tricky. So, in that case, you want to go ahead with Exadata.

Overall, I rate IBM Netezza Performance Server a seven out of ten.

Get the requirements and have them finalized. Then, be very specific about the requirements that your organization needs. Based upon your requirements:

1. Identify whether Netezza will be suitable for your requirements. 
2. Get the sizing right.

Resources who have previously worked with Netezza should be asked to work on the project. If people with prior Netezza knowledge cannot be engaged then candidates who are familiar with Linux should be sent for Netezza training offered by IBM prior to engaging them to work on this platform.

Netezza is a great option for data warehousing, but give due attention to concurrency and find out how much would be the peak load the database may have to handle. Also, check whether performance is acceptable for APIs and web services. Performance may not scale for thousands of single row lookups, as the database is more suited for complex aggregated data warehousing queries.

I rate IBM Netezza Performance Server a seven out of ten.

1. Netezza is well suited for data warehousing and analytics, not for OLTP application
2. The key approach is to develop an uniform data distribution scheme and collocation of data partitions across related database objects. For example, if we have a large customer dimension and a large sales by customer fact, these tables will be joined very frequently. To get the best performance, both tables should be distributed on the same key, e.g. customer_id.

Try to find someone who had already worked with this appliance to have some tips and advices to help you to use it as better as it can. I take too long to discover the best way to make it work well. With my team, I have created a data environment using Netezza as Data warehouse solution, ODI to run the ETL process, shell script. We have now five years of data stored in the Netezza database and we distribute data to all BI Applications easily and quickly. However, it would be better if we had some useful help in the past.

My client is looking towards replacing Neteeza with one of the up and coming warehousing solutions like Presto. They don't want the in-house or on-prem cost of managing that particular appliance. When everything is available on cloud, we pay less. My client develops medical products. They wanted to concentrate on the medical part, not on how to manage their IT. So they're moving towards more and more towards the cloud to replace the on-prem solution.

My advice would be to fully categorize your needs. Why you need Netezza should be a specific question, because there are so many different analytic solutions and which provide performance and which are cheaper than Netezza. Until you figure out completely that you only need a PDA (pure data analytics) system, you should really look at other products and compare them.

I wouldn't choose Netezza in today's world when we have Redshift, Presto, EMR, when we have Teradata, and when we have Oracle Autonomous. In today's world, you should look at these solutions first. If they don't serve your purpose, then look to Netezza.

In the current world, data is the big question. Nowadays, we are receiving a lot of data. It's like the data generation has come. We have terabytes of data and it might be, in a year or so, you cross the petabyte scale. So go with a petabyte-scale solution instead of a non-expandable Netezza appliance.

We are currently working on the latest Mako version. After that - Mako retires in 2024 - I don't think they have anything on Netezza. What they have is dashDB and Sailfish, which is a completely different product for IBM, but similar to Netezza. And those are expandable.

Netezza is a good product in and of itself, aside from the fact it is not expandable. Overall, it's a good product but definitely has room for improvement.

You can definitely consider this appliance if you have:

• A large volume of processed data (tables) that are created on a daily basis
• Data that requires daily analysis, critical for decision making, and a budget to complement it.

This is one of the most stable and fastest data warehouse appliances available in the market today.

Netezza should have enough advantages with implementation, i.e time to deployment, price, performance, and the ability to integrate with the existing environment.

Based on first conception, do a POC, scale up to the volumes and get the vendor to prove that it can work with their requirements. Get them to scale it up, either simulate it, make sure it can actually do what it says, rather than buying beta and then get it and then find out that it doesn't actually do everything it says it does.

The most difficult time I have with people is getting them to understand that Netezza is not meant for individual transactions, but for full set processing.

IBM support is very good for this product. It has very few issues and it does exactly what it says on the tin. Check for the functional limitations of the logical database e.g there are no such thing as indexes/primary key constraints where you might want to force uniqueness.

If volume is the issue, use Netezza. Nothing is better than this product.

Any potential customer who has an inclination towards large scale analytics, should consider Netezza as an option. This not only gives a faster response, but you can also save on resource cost compared to other MPP's. Netezza's maintenance cost is quite low and this will give you an edge for long term revenue growth.

It is good product if you are choosing to go for datawarehouse business intelligence.

I rate Netezza at four out of 10. There is not too much involved to set one up from a customer perspective, but after the initial setup it is pretty awful on the customer support side of it.

My advice would be, check out all options. Don't just go with big-name vendors, because that is not always going to be the right answer.

The most important criteria when selecting a vendor for a data warehouse solution are, obviously, the speed and the ability to handle large amounts of data. That's especially true from an analysis standpoint, and having it not only do the math and select statements but also do more aggregation and analysis-type queries.

The speed has been excellent for us, in pulling information, as well as the batch timing, and the suite of tools that comes with it for the ETL withIBM InfoSphere. Also, the data governance prospect, as a company we haven't really delved too far into that, but from what I've seen, that is a really powerful tool as well, to help with data lineage and keeping track of that. So the speed is good and the suite of tools seems to be very beneficial.

From my standpoint, I would give it a nine out of 10. It has done everything that we needed it to do, it's great. The only reason I wouldn't give it a 10 is because, early on, there were a couple of maintenance things that we had to do.

It is easy to use. Make sure you select the right ETL and reporting tool. Also select the right tool for the organization to hold it in the long run.

It has a compression engine and FPGA on but you should still analyze your volume of data and decide on the right model and size.

It is a very good product. Like always, good people with good expertise will help a lot

It's fit for the purpose it's designed for. It's an analytical/hierarchical database, now in great demand, that can store plenty of data and return the results in no time for complex queries.

Best if you have a robust infrastructure, where network bandwidth is good. We used 10GB Ethernet cable for data transfer.

Every query has to be set based - no iteration over a result set. stored procedures should be used sparingly.