Google BigQuery vs. Oracle Exadata

Google BigQuery is great for being the central datastore and entry point of data if you're on GCP. It seamlessly integrates with other Google products, meaning you can ingest data from other Google products with ease and little technical knowledge, and all of it is near real-time. Being serverless, BigQuery will scale with you, which means you don't have to worry about contention or spikes in demand/storage. This can, however, mean your costs can run away quickly or mount up at short notice.

Incentivized

• First, get the database on Oracle. If you are in an Oracle stack, it would be much better to use the Oracle products. If you are driving a Ferrari, you wouldn’t put a Mercedes engine in it. If you are writing a query, you cannot rely on other brands. Since I'm an architect, when I look for a product, I look for performance.
• The installation is easy because it comes out-of-the-box and you just start using it.
• Previous to Oracle Exadata, we were using a normal Oracle RAC service. We were just waiting for this product to come out.
• I'm currently writing a data warehouse on Exadata. Before this solution, we were aiming for this to be completed by 8 a.m., when our ETLs would finish. With the help of Exadata's special features, this was reduced to 3 a.m. This solution allows us to bring more data within the same time period. It provides us with more subject areas that provide more reports to our users. Our ETL times reduced to 65%, then to 50%.

Incentivized

• Its serverless architecture and underlying Dremel technology are incredibly fast even on complex datasets. I can get answers to my questions almost instantly, without waiting hours for traditional data warehouses to churn through the data.
• Previously, our data was scattered across various databases and spreadsheets and getting a holistic view was pretty difficult. Google BigQuery acts as a central repository and consolidates everything in one place to join data sets and find hidden patterns.
• Running reports on our old systems used to take forever. Google BigQuery's crazy fast query speed lets us get insights from massive datasets in seconds.

Incentivized

• Customize-able for specific functionality optimized for combination of online transaction or analytical processing.
• Ability to serve mix workloads with resource management feature enables prioritizing allocation for certain workload.
• Scale-able on-premise with compatibility for cloud deployment offers flexible solution for organization considering to transition from on-premise solution.

Incentivized

• It is challenging to predict costs due to BigQuery's pay-per-query pricing model. User-friendly cost estimation tools, along with improved budget alerting features, could help users better manage and predict expenses.
• The BigQuery interface is less intuitive. A more user-friendly interface, enhanced documentation, and built-in tutorial systems could make BigQuery more accessible to a broader audience.

Incentivized

• Patching can often become quite involved and convoluted. It should be more transparent and straightforward.
• Storage metrics can be difficult and time consuming to obtain.
• Basic administrative functions can be hard to repair when discovered.
• Vendor support can take a while to obtain. Generally several attempts are necessary to reach the right area of vendor expertise.

Incentivized

We have to use this product as its a 3rd party supplier choice to utilise this product for their data side backend so will not be likely we will move away from this product in the future unless the 3rd party supplier decides to change data vendors.

Incentivized

web UI is easy and convenient. Many RDBMS clients such as aqua data studio, Dbeaver data grid, and others connect. Range of well-documented APIs available. The range of features keeps expanding, increasing similar features to traditional RDBMS such as Oracle and DB2

I am comparing Exadata with the Oracle RAC database experience. In addition to Oracle RAC features, Exadata provides automatic performance optimization through Smart Scan and storage indexes. Deep integration with the Oracle ecosystem and tight coupling with Oracle Enterprise Manager
for monitoring and management. Some downsides of Exadata are: a steep learning curve, concepts like cell offloading, IORM, and flash cache behavior aren’t intuitive initially. Operating
Exadata requires specialized DBA skills.

Incentivized

I have never had any significant issues with Google Big Query. It always seems to be up and running properly when I need it. I cannot recall any times where I received any kind of application errors or unplanned outages. If there were any they were resolved quickly by my IT team so I didn't notice them.

Incentivized

I think Google Big Query's performance is in the acceptable range. Sometimes larger datasets are somewhat sluggish to load but for most of our applications it performs at a reasonable speed. We do have some reports that include a lot of complex calculations and others that run on granular store level data that so sometimes take a bit longer to load which can be frustrating.

Incentivized

BigQuery can be difficult to support because it is so solid as a product. Many of the issues you will see are related to your own data sets, however you may see issues importing data and managing jobs. If this occurs, it can be a challenge to get to speak to the correct person who can help you.

Incentivized

Google BigQuery of course collects a much much larger array of raw data and can handle (practically) an unlimited amount of data. For a large enterprise like ours that relies on large-scale analytics, this is absolutely imperative. Google BigQuery can also combine GA4 data with external sources (like CRM tools), so our analytics can be unified. Due to our heavy reliance on GA4, Google BigQuery is the natural choice since it is a Google product and has better integration.

Incentivized

I couldn’t find all the options listed here, so I’m
summarizing the ones we considered during our evaluation before selecting
Oracle Exadata Service on AWS:


Continuing
to use the Oracle RAC on‑premise database
Running
Oracle Database on AWS EC2
Using
Oracle Database through the AWS RDS service


Since we wanted to retain Oracle RAC capabilities while
achieving high performance and maintaining our presence in the AWS public
cloud, we selected the Oracle Database @AWS Exadata service.

Incentivized

We have continued to expand out use of Google Big Query over the years. I'd say its flexibility and scalability is actually quite good. It also integrates well with other tools like Tableau and Power BI. It has served the needs of multiple data sources across multiple departments within my company.

Incentivized

• In some places, Google BigQuery has helped us save some money by avoiding the need for expensive infrastructure and reducing some of the operational costs.
• Scalability is up-to-date and really helpful in multiple places.
• Knowledge transfer is easy as it is very user-friendly, so the learning curve has been reduced.
• Also, it gives us more insights from our data, helping us make smarter decisions for our business.

Incentivized

• One of the central critical systems was migrated from a large 4-node Oracle RAC running on legacy hardware. This application was experiencing severe performance issues literally causing loss of service for numerous customers. Once it was migrated to a 2-node Exadata server, its average performance improved almost by a level of magnitude, therefore eliminating any signs of application slowness.
• Numerous application databases were migrated to Exadata servers which reduced the overall cost of hardware due to Exadata's price structure.

Incentivized