We previously used Teradata which is a much better product but it was super expensive, around five times more than Greenplum. We had other reasons for moving to Greenplum including the super fast analytics it provides. 

We have used Snowflake, Oracle, and many such solutions.

We were using Sybase and handling massive data, bulk operation was not possible.

Before I joined this company, I used different data warehousing solutions.

Making the transition to Greenplum requires a completely different mindset because it is massively parallel. It's more like a Big Data mindset, where you need to consider that you are distributing data between cluster nodes. It is not always straightforward to make the switch.

We also use Cloudera and Oracle so we have a few alternatives. We currently use Greenplum because one of our customers needed an open-source solution that would scale well and after some investigation, we went with Greenplum. 

We tried other MPP’s.

This has just been used for POC period not for a regular use.

We were one of pioneers in adopting this solution. So we got the best deal when compared to the competitors in several areas.

The purchase of Greenplum was our first interaction with Pivotal. We have been a customer of EMC for a very long time.

We did use other products in the company but it wasn’t an MPP architecture database. Our data was getting bigger so we needed something with MPP architecture to tackle big data challenges so Greenplum was considered. It was a management decision to purchase this product (not sure whether other similar products were considered or not)

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

We used to other products before, but when we worked with Greenplum, as compared to other products on the market, we found it's a good product.

Before Greenplum, we used Oracle but it was mostly obsolete. So we had to upgrade our tools. We needed to have a database with an API tool.

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

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

We used Oracle previously. We based our choice on expertise in our US operation, where we have a GreenPlum expert who provided some amazing use case examples to help us in our selection process.

No solution was used previously.

We applied MPP Appliance for the first time earlier we were running on SMP’s.

There was no other solution used previously.

We were using MySQL prior to this solution.

Yes, Oracle Exadata. Performance was the main criteria for switching to Greenplum.

Used Greenplum originally. We have evaluated other products; the final decision is based on ROI

Yes, we have Oracle Exadata.

I used Oracle Enterprise edition – moving to Greenplum due to the MPP (it’s like Map-Reduce). I prefer a SQL solution rather Hadoop or whatever – especially if you’re moving from RDBMS. Now I’m also using Amazon Redshift from the same reason and also we don’t need to manage any server, it’s only a service and this is our best option especially because we’re already using Amazon.

Previously, there was Oracle database, and the EMC Greenplum database was used for better performance from larger data volumes because it uses massively parallel processing. This increased the performances multiple times while reducing time needed for optimization of database queries.