We performed a comparison between BigQuery and Oracle Exadata based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Warehouse solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The integrated data storage features are good."
"We like the machine learning features and the high-performance database engine."
"BigQuery excels at structuring data, performing predictions, and conducting insightful analyses and it leverages machine learning and artificial intelligence capabilities, powered by Google's Duarte AI."
"It's pretty stable. It's fast, and it is able to go through large quantities of data pretty quickly."
"The main thing I like about BigQuery is storage. We did an on-premise BigQuery migration with trillions of records. Usually, we have to deal with insufficient storage on-premises, but in BigQuery, we don't get that because it's like cloud storage, and we can have any number of records. That is one advantage. The next major advantage is the column length. We have some limits on column length on-premises, like 10,000, and we have to design it based on that. However, with BigQuery, we don't need to design the column length at all. It will expand or shrink based on the records it's getting. I can give you a real-life example based on our migration from on-premises to GCP. There was a dimension table with a general number of records, and when we queried that on-premises, like in Apache Spark or Teradata, it took around half an hour to get those records. In BigQuery, it was instant. As it's very fast, you can get it in two or three minutes. That was very helpful for our engineers. Usually, we have to run a query on-premises and go for a break while waiting for that query to give us the results. It's not the case with BigQuery because it instantly provides results when we run it. So, that makes the work fast, it helps a lot, and it helps save a lot of time. It also has a reasonable performance rate and smart tuning. Suppose we need to perform some joins, BigQuery has a smart tuning option, and it'll tune itself and tell us the best way a query can be done in the backend. To be frank, the performance, reliability, and everything else have improved, even the downtime. Usually, on-premise servers have some downtime, but as BigQuery is multiregional, we have storage in three different locations. So, downtime is also not getting impacted. For example, if the Atlantic ocean location has some downtime, or the server is down, we can use data that is stored in Africa or somewhere else. We have three or four storage locations, and that's the main advantage."
"The product’s most valuable feature is its ability to manage the database on the cloud."
"BigQuery is a powerful tool for managing and analyzing large datasets. The versatility of BigQuery extends to its compatibility with external data visualization tools like Power BI and Tableau. This means you not only get query results but can also seamlessly integrate and visualize your data for better insights."
"It has a well-structured suite of complimentary tools for data integration and so forth."
"It is a highly relevant option with extreme performance."
"The most valuable feature of Oracle Exadata is the smart scan. We have large TB sessions of approximately 100 per second for each of our three instances. The smart scan allows us the obtain data in time in the enterprise manager."
"What I found most valuable in Oracle Exadata is its newer technology that gives better performance. It has more recent hardware and significant changes in the architecture, so it's better than older solutions."
"The performance of the data is the most important part."
"It has improved the performance, now we run with more performance cores with less CPU to attend all the database demands. Reducing Time to Market, increase our ability to face the competition with speed and low cost."
"Exadata's best features are its performance during redo logging and the elasticity of the database handling."
"Oracle Exadata has very good hardware."
"The most valuable feature of Oracle Exadata is its capabilities for storing and processing data. It is very good for our domain."
"There are some limitations in the query latency compared to what it was three years ago."
"The initial setup could be improved making it easier to deploy."
"It would be better if BigQuery didn't have huge restrictions. For example, when we migrate from on-premises to on-premise, the data which handles all ebook characters can be handled on-premise. But in BigQuery, we have huge restrictions. If we have some symbols, like a hash or other special characters, it won't accept them. Not in all cases, but it won't accept a few special characters, and when we migrate, we get errors. We need to use Regexp or something similar to replace that with another character. This isn't expected from a high-range technology like BigQuery. It has to adapt all products. For instance, if we have a TV Showroom, the TV symbol will be there in the shop name. Teradata and Apache Spark accept this, but BigQuery won't. This is the primary concern that we had. In the next release, it would be better if the query on the external table also had cache. Right now, we are using a GCS bucket, and in the native table, we have cache. For example, if we query the same table, it won't cost because it will try to fetch the records from the cached result. But when we run queries on the external table a number of times, it won't be cached. That's a major drawback of BigQuery. Only the native table has the cache option, and the external table doesn't. If there is an option to have an external table for cache purposes, it'll be a significant advantage for our organization."
"I would like to see version-based implementation and a fallback arrangement for data stored in BigQuery storage. These are some features I'm interested in."
"When it comes to queries or the code being executed in the data warehouse, the management of this code, like integration with the GitHub repository or the GitLab repository, is kind of complicated, and it's not so direct."
"I rate BigQuery six out of 10 for affordability. It could be cheaper."
"They could enhance the platform's user accessibility."
"The process of migrating from Datastore to BigQuery should be improved."
"One small area for improvement in Oracle Exadata is integration, particularly at the consolidated application level."
"There's room for improvement in terms of deployment, as it could be made faster and more user-friendly."
"We need a monitoring tool which can in one place, where we can manage, monitor the entire Exadata components."
"License or upgrade management can be difficult and time consuming because it requires login to a separate console."
"Setting up Exadata is complex. You need an Oracle vendor or someone who is Oracle-certified to set it up."
"It would be nice to have a single click button to, say, migrate my VMware VM into the Oracle VM, or vice-versa."
"I have found Oracle Exadata to be scalable. However, you have to purchase more hardware, such as memory."
"In a future release, I would like to see some upgrade analysis advisors to help with a clear roadmap on steps that need to be taken and some of the automated processes."
BigQuery is ranked 5th in Cloud Data Warehouse with 31 reviews while Oracle Exadata is ranked 2nd in Data Warehouse with 125 reviews. BigQuery is rated 8.2, while Oracle Exadata is rated 8.4. The top reviewer of BigQuery writes "Expandable and easy to set up but needs more local data residency". On the other hand, the top reviewer of Oracle Exadata writes "Offers a variety of valuable features". BigQuery is most compared with Snowflake, Teradata, Oracle Autonomous Data Warehouse, Vertica and SAP Business Warehouse, whereas Oracle Exadata is most compared with Oracle Database Appliance, Teradata, Oracle Autonomous Data Warehouse, Snowflake and Teradata Cloud Data Warehouse. See our BigQuery vs. Oracle Exadata report.
See our list of best Cloud Data Warehouse vendors.
We monitor all Cloud Data Warehouse reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
