We performed a comparison between Oracle Exadata, TIBCO Live Datamart, and Vertica based on real PeerSpot user reviews.
Find out what your peers are saying about Snowflake Computing, Oracle, Teradata and others in Data Warehouse."This product can noticeably enhance performance of contextual Oracle databases."
"The most valuable feature of Oracle Exadata is the storage available."
"Parallelism is the most valuable feature."
"On-premises Exadata is just as stable as the cloud version. It's a very stable platform."
"Oracle has reliable solutions and this one is no different."
"The offloading of data to the SIM is a valuable feature."
"It is a highly relevant option with extreme performance."
"The most valuable feature is that you have the same familiar environment of an Oracle database but with the additional performance you get from this architecture."
"You can create your own rules that include mathematic calculations."
"The solution has a powerful aggregating feature"
"Vertica is a columnar database, this support our developments in analytics, advanced analytics, and ETL process with large sets of data."
"We are able to integrate our Vertica data warehouse with Tableau to create numerous reports quickly and efficiently."
"Its analytics has enabled Pythian's clients to get the business insights as quick as they wanted. Its lower maintenance has also improved the ROI."
"Eighty percent of the ETL operations have improved since implementing this solution."
"I like the projection feature, which increases query performance."
"Vertica has a few features that I like. From an architecture standpoint, they have separated compute and storage. So you have low-cost object storage for primary storage and the ability to have several sub-clusters working off the same ObjectStore. So it provides workload isolation."
"The most valuable feature of Vertica is the ability to receive large aggregations at a very quick pace. The use case of subclusters is very good."
"Vertica enabled us to close large deals. Customers with large data sets had to be migrated from PostgreSQL to Vertica due to performance."
"There is a feature for security, but it is not included in the first purchase of this solution. That means if you need to increase the security, you need to buy the security feature which doesn't come by default on these solutions."
"There is room for improvement with the handling of the Temp IO, which is often used for JOIN statements."
"The solution's pricing is very high."
"The customization can sometimes be difficult to achieve."
"Oracle Exadata could improve by having faster data retrieval. We receive data at four or five seconds and want to reduce that number to one second."
"We had issues with system restoration."
"It's too expensive per terabyte. It's complex."
"A room for improvement in Oracle Exadata is that it's not very easy to use in a microservices environment. It's not easy to split databases, and if this was easier to do in Oracle Exadata, it would make the solution better. What I'd like to see in the next release of Oracle Exadata is for it to become more modular, so you can use it in a context where the data layer is spread between many independent services."
"Improvements need to be made on the load balancing side."
"The solution's setup could be quicker and easier."
"The documentation of Vertica is an area with shortcomings where improvements are required."
"Documentation has become much better, but can always use some improvement."
"Some of our small to medium-sized customers would like to see containerization and flexibility from the deployment standpoint."
"When it is about to reach the maximum storage capacity, it becomes slow."
"Fact-to-fact joins on multi-billion record tables perform poorly."
"Monitoring tools need to be lightweight. They should not take up heavy resources of the main server."
"The integration with AI has room for improvement."
"Vertica seems to scale well, except for one use case where you are on a multi-node cluster. For example, if you had a nine-node cluster, one node goes down, then the eight nodes don't scale, because the absence of the node is very apparent, which is a problem. If you have nine nodes or multiple nodes, the whole idea is that if one of those nodes goes down, then you should not see an impact on the system if you have enough capacity. Even though we have enough capacity, you can still see the impact of the one node going down."