VMware Tanzu Data Solutions Reviews

Append Only tables, data compression and bulk load and extraction using External Tables are very valuable features for us.

We have improved our quarterly statements turnaround dramatically and could sustain for increasing data.

With the ORCA optimizer the earlier Append-Only feature has been upgraded to Append-Optimized where now we can update the data on earlier Append-Only tables just like any other heap tables. But I found this has increased the time taken for Vacuum Analyze operation on these tables like from 10 mins to 1 hr + (on large tables). In our case we don't need an update on our Append Only tables and hence this became a drawback. VA on Append-Optimized tables need to be improved.

Backup & Restore performance need to be improved.

ORCA optimizer when turned on is not showing consistency. Some workloads shows improved performance and some workloads became very slow. This need to be improved for consistency.

I have used it for about 4 years now.

Pre ORCA version was stable. ORCA release is not stable. Some workloads slowed down with new release even when the new optimizer is not turned ON.

Tech support is average. They lack information about new features in the new releases and the possible impact of them.

Earlier we were using OLTP based RDBMS solution. We realized we needed a OLAP solution and also something that can scale horizontally.

The most valuable feature of Greenplum is the Massively Parallel Processing (MPP).

With this solution, we've reduced load on the OLTP systems.

The fact GreenPlum is using an older version of Postgres means developers coming from other products will find many missing features in PostgreSQL, features which you would assume are standard.

Greenplum is based on Postgres 8.2.15 which was released in 2009. While the SQL syntax and functionality has continued to evolve in other platforms in the ensuing years it appears to have stagnated in Greenplum.

We haven't had any issues with deployment.

It's been stable for us.

It's scaled for our needs.

The community around GreenPlum is very small, making it difficult to learn from others experience via forums or blog posts.

We can integrate the Hadoop with DCA V2. This will be huge development in the big data technologies.

It increased the read/write process because of it MPP architecture.

EMC already developed DCA V3, But if the hardware is little stable, I prefer DCA V2.

I am from a support background, and have used this on multiple accounts, for the last four years.

There have been no issues with the deployment.

Hardware failure is a concern.

We have had no issues scaling it for our needs.

Technical support is excellent.

I know many customers are migrating from Oracle to Greenplum due to its faster processing.

It is straightforward,open source system.

Better chose EMC to perform the implementation. More over, it is not complex and we can do it easily in our environment with a little knowledge.

Greenplum is an opensource system, but they do charge for support.

Installation is very simple, make sure to set the configuration values based on the requirement.

The most valuable features are MPP and that it's polymorphic.

We have a set of workflow flows that takes 10 hours in Oracle Exadata, now it takes 4 hours with EMC Greenplum.

It doesn't work as efficiently as we'd like because it requires more segment node capacity (size, RAM, CPU) than we currently have.

I've used it since 2013.

At the moment, we don't have any issues with deployment.

At the moment, we don't have any issues with stability.

At the moment, we don't have any issues with scalability.

8/10

8/10

Yes, we have Oracle Exadata.

The initial setup is straightforward. It was simple for our personnel to install on the Unix system and network.

It's a good product when comparing the price to its functionalities.

You should consider the capacity of your data before you buy it.

• Parallel Processing and Data Distribution based architecture.
• HA built-in with mirroring.
• Highly configurable and lots of tuning features.

• This has helped us bring down our end-to-end EDW load time to 1/3 the time.
• It has enabled faster and efficient data analysis.
• Scalable environment without adding too much cost.

• It needs a much more robust and user friendly monitoring and management front-end tool.
• More stability and auto-recovery with the segments.
• Report generations on system health and recommendations.

I've used it for two years.

Up to now, we've had no issues with deployment.

Up to now, we've had no issues with stability.

Up to now, we've had no issues with scalability.

The response is fairly good but would like more support from the R&D on more complex issues. Also, they need to ensure there are logs that can be used without causing any downtimes to the system for any case analysis.

It's a highly efficient and faster DB with lot of features at much less cost to that of other MPP DB’s evaluated.

It was complex as we have to code convert everything into GP functions so as to best be able to use the GP parallel. Pushdown feature was not available via Informatica. The initial parameter setup took quite some time to test to get the sweet spot for performance.

In-house with vendor support.

Make sure you have the designs, approaches and architecture in place before kicking of the implementation. Its best to have someone involved with prior migration experience.

Processing speed of queries used for ‘Reporting’ solutions is the most valuable feature.

Not Applicable for the area I was responsible for, as we ended up migrating away from Greenplum.

Stability and scalability for large number of concurrent applications & their users. The results we got were very inconsistent, depending on number of connections taken up by multiple applications and users.

When our application was first deployed using Greenplum, the number of users of the rrack on which Greenplum was deployed was very limited. We got excellent query performance results at that time. But as more applications started getting deployed, we started getting very inconsistent performance results. Sometimes the queries would run in sub-seconds, and sometimes same queries would run 10 times longer. The reason we found this was that Greenplum limits the number of active concurrent connections. Once all connections are being used, any new query gets queued, and thus response time suffers.

The impression we got was that the EMC Sales team that sold Greenplum to the organization did a great job. But later on the ball was dropped when it came to educating on which type of applications are suitable to Greenplum , and how to configure it to get optimal performance. When Pivotal took over support of Greenplum, their consultant visited us to go over the issues we were having. He advised us that Greenplum is not the best environment for our application needs. We ended up migrating our application out of Greenplum, along with a few other applications.

There was no issue with the deployment.

There were issues with the stability.

There were issues with the scalability.

Ensure that this is the right tool for your needs. For instance, Greenplum is not the best tool for cases where data has to be kept up to date in real time. Capacity planning is key to success, once you do decide it is the right tool for you.

• Distributed data for performance
• File loaders to reduce dependency on Informatica

Batch processing times have dramatically decreased from over 12 hours to under three hours. Much of this is converting off of Informatica and using distributed processing. Reporting performance also improved greatly.

Since we are upgrading to a new version at this time, it’s hard to say. But we seem to be replacing a disk on the appliance every week.

I've used it for six years.

There's no issues, although we are currently in the middle of an upgrade to v4.3.5.

It seems like we are replacing a disk on the appliance every week. Not a noticeable issue for users and batch processing is not adversely impacted.

Very good. Response times are good for service calls.

I believe the set-up was straightforward. I don’t remember any issues.

We used a vendor team. My advice is that the planning is critical. When converting processing jobs, convert them to PostgreSQL for better performance. Yes they could work as written previously, but you benefit using the features of the product immediately if you adjust the processing to match appliance. Use the bulk processing to your advantage.

We evaluated other solutions. Not sure of the reasons why this product was chosen.

It’s a good product. We moved from Oracle and I don’t want to go back.

The Greenplum loaders – their methods, insert, update and merge – were most valuable. The external table feature within Greenplum was also very valuable in achieving performance and scalability

A lot of customers use Greenplum and for their ETL use cases they use Informatica PWX for Greenplum, which helps them achieve transfer of data from a number of data sources into Greenplum. We can help customers to load data effortlessly and quickly.

It would be best if Greenplum would support array writes through ODBC drivers . Currently through Data Direct Greenplum drivers we can have single row inserts into Greenplum only. It would help if array loading is supported.

I have been using Greenplum loaders to load data into GreenPlum for three years.

There were no issues in deploying it.

The external table feature helps to make this a stable solution.

It scales to our and our customers needs as required.

The ongoing response from their support on certain technical issues has been slow. It would help if we can have a faster turn-around here.

There was no other solution used previously.

The installation and configuration is straightforward.

We implemented through a in-house team . The overall solution will be useful and is not complex

If the use case is going to be requiring a huge data transfer and big data analytics. This is a good product to use.