TrustRadius: an HG Insights company
Google BigQuery Logo

Google BigQuery Reviews and Ratings

Rating: 8.6 out of 10
Score
8.6 out of 10

Community insights

TrustRadius Insights for Google BigQuery are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Quick Data Analysis: Users appreciate the rapid query speed of Google BigQuery, enabling them to analyze massive datasets without long wait times. The fast query performance is a significant advantage highlighted by users for efficient data processing and analysis.

User-Friendly Interface: Many reviewers find Google BigQuery very user-friendly, allowing team members with varying levels of expertise to easily query data using simple language. The intuitive interface of Google BigQuery's editor and query builder is noted as helpful in quickly constructing new queries by users.

Seamless Integration: Users value the seamless integration of Google BigQuery with other tools like Google Cloud Storage and Data Studio, enhancing workflow efficiency and collaboration. This integration capability with various tools contributes to improved data management solutions according to users' feedback.

Reviews

79 Reviews

Perfect for Big Data Datawarehousing

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We use Google BigQuery as the company's data warehouse. We also have some stored queries that levarage the scheduling feature of Google BigQuery. And we use it to connect to some google sheets files we have online so that we can make queries over them using SQL and perform som data analysis

Pros

  • Scheduling
  • User Interface
  • SQL editor
  • Gemini companion

Cons

  • Lack of relationship between tables
  • unpredictable costs
  • Data loading delays

Likelihood to Recommend

overall, Google BigQuery is a powerful tool for large scale data analysis and warehouse management, specially when you use a lot of products from google cloud's products. However, it is not well suited when it comes to real time processing or transactional workloads. In such cases, firebase or cloud sql might be more appropriate

BigQuery -Easy to Learn Best to use

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

we are using Store all data that we have. It has proven to be a very good product where we have been easily able to migrate to from our Excel sheets and create a combined database where we store all our historical data across clients and different teams and provide a place where they can access the data easily.

Pros

  • Storage
  • Speed
  • Easeof use

Cons

  • Excel upload
  • Integration with third parties
  • More google sources

Likelihood to Recommend

if the data is not huge and we don’t need a lot of cloud storage features such as high processing, immediate retrieval of data, et cetera. Then they might be the solutions which are better

Vetted Review
Google BigQuery
3 years of experience

Google BigQuery, the big thing

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

We have UI survey reporting database in Google BigQuery.

It is meant to give insights of how the users or sales people like the user experience.

We recieve files which finally gets loaded in gcp env.

Querying tables In Google BigQuery gives fast insights with comparatively less time than other cloud dbs.

Pros

  • Compatibility with traditional ETL tools
  • Time travel
  • Columnar storage
  • An intuitive UI

Cons

  • Not very Easy Integration with spark
  • Data lineage tool kind feature is not there
  • Orchestration can be better

Likelihood to Recommend

I feel like Choosing it when we have Streaming data with pub sub playing a big role.

Though streaming analytics can be a lil.challenging when you have real time insights needed fast.

Much suited for micro batches or batch data.

You can create a big data warehouse store history.

Batch is where I would prefer

Good BigQuery: Speed, Scale, and Simplicity

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

I use Google BigQuery to run codes on Telecom customers to understand their connect and disconnect behavior. Some of the key business problems that I have solved using Google BigQuery is mapping geospatial data with zip/market zones to enhance our product sales by reaching the correct/targeted audience. Apart from this I use it to understand churn trends - why customers are moving/disconnecting, what's working, how to streamlines offers etc.

I also utilize it to understand demand and what is driving customers to take up an offer.

Pros

  • Ability to upload custom data set to use on Google BigQuery - especially when I have to use Longitude and latitude
  • Ability to handle large amount of data without affecting processing speeds
  • Ability to integrate with other cloud services like Google Data Studio, Google Sheets, and Google Cloud Machine Learning Engine. This makes it easier to build comprehensive data solutions within the Google Cloud ecosystem

Cons

  • Optimization: Google BigQuery can sometimes struggle with optimizing very complex queries, especially those involving multiple joins and subqueries.
  • Error/Failure check: It would be good to have a feature that can tell exactly where the coding issue would be along with suggesting some alternate codes - this will help give people an idea of what's wrong and what can we do about it

Likelihood to Recommend

1. Complex Query Optimization Issues: Sometimes optimizing very complex queries involving multiple joins and subqueries becomes difficult and ends up taking time to process

2. Outside source data integration that works: Working on in-built libraries or data has helped me improve working, especially Zillow

The best and only choice for an Analytics Database.

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use Google BigQuery as our main analytics database, as a data warehouse. It addresses our need for having all our data, from different sources, be available for analysis and flexible querying.

Pros

  • Storing large amounts of data
  • Querying large of amounts of data
  • Serving as a unifying data source for all kinds of data from different sources
  • Zero devops or infrastructure work required
  • Extremely good value for money ratio

Cons

  • Query syntax is sometimes a little hard
  • Data exploration tooling could be better

Likelihood to Recommend

I would 10/10 use Google BigQuery as an analytics DB again and again. It's perfect for it, really easy to use both for sending and ingesting data and also for retrieving and querying the data. It also has lots of integrations in 3rd party products, ranging from visualization to AI, as it is a widespread solution.

I would not use it for a production database, as it has relatively high latency and is priced per query, so it doesn't really work in that scenario.

Vetted Review
Google BigQuery
10 years of experience

Good choice for cheap data usage

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

For data analysis by our enterprise data team, primarily. Most activity gets dumped into Google BigQuery in one form or another to support enterprise reporting. We also use it for creating Pub/Sub ledgers, using the Google BigQuery Pub/Sub subscription type. This allows us to debug and research data that has flowed through a topic.

Pros

  • good pricing
  • SQL for querying
  • query against JSON in fields

Cons

  • UI feels dated
  • JSON querying could be simplified

Likelihood to Recommend

Where low cost, low frequency of access is needed for working with large datasets.

Vetted Review
Google BigQuery
3 years of experience

Seamless and near real-time integration for GCP users.

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

BigQuery fits naturally into the GCP estate, seamlessly integrating with GSheets and allowing users to ingest data into BigQuery with little to no technical knowledge. This is beneficial for GForm data, which is naturally presented via GSheet. With the real-time integration GSheets has with BigQuery, this form of data can then be in your data stack in mere seconds. This is really helpful when we want to collect feedback data or review a process using GForms as the method of data collection.

Pros

  • Realtime integration with Google Sheets.
  • GSheet data can be linked to a BigQuery table and the data in that sheet is ingested in realtime into BigQuery. It's a live 'sync' which means it supports insertions, deletions, and alterations. The only limitation here is the schema'; this remains static once the table is created.
  • Seamless integration with other GCP products.
  • A simple pipeline might look like this:-
  • GForms -> GSheets -> BigQuery -> Looker
  • It all links up really well and with ease.
  • One instance holds many projects.
  • Separating data into datamarts or datameshes is really easy in BigQuery, since one BigQuery instance can hold multiple projects; which are isolated collections of datasets.

Cons

  • Can't customise compute methods.
  • In some cases, it's nice to limit a specific query, user, database, or process to a specific compute engine. This helps standardize costs, run time, and the fallout on shared resources. BigQuery's ease of use makes it simple for most users but difficult to customize for power uses.
  • Potential for vendor lock-in.
  • If your data stack is heavily reliant on integrations with other GCP products, you'll find it hard to move. Even if you just move from BigQuery to another supplier, you'll need to set up integrations from your current GCP products to the external vendor. Or find a vendor that integrates with GCP well.
  • Autoscaling might cause unexpected costs.
  • Since BigQuery charges on storage, compute, and streaming inserts, if any of these become unexpectedly in-demand (especially compute), your costs may skyrocket without much notice.

Likelihood to Recommend

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.

Vetted Review
Google BigQuery
7 years of experience

Honest review about G bigQuery.

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use BigQuery to analyze marketing campaign performance, track customer engagement, and optimize marketing strategies for over 40 clients. This involves processing large volumes of data from various marketing channels. BigQuery supports real-time data ingestion and analysis, enabling us to find problems and make quick and informed business decisions. BigQuery’s flexible pricing allows us to manage costs effectively based on client budgets.

Pros

  • SQL Capabilities like insert,update, delete.
  • Real-Time Data Analysis.
  • It allows me and my clients to build and deploy machine learning.

Cons

  • High costs if not monitored closely.
  • Limitations on the number of API requests.
  • Complex Query Optimization.

Likelihood to Recommend

I have a big e-commerce company that needs to analyze transaction data from millions of customers. Thanks to BigQuery, I do that quite well. I analyze customer behavior to understand purchasing patterns, preferences, and trends. Managing inventory levels in real-time to ensure products are always in stock. Providing personalized product recommendations

Google BigQuery Review

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We use BigQuery to store and analyze data for identifying long term trends. Data is ingested through pipelines on Airflow. Since our other logging solutions were only storing information for less than 2 months it was very difficult to identify the overall trend and seasonality. Using BigQuery, we are not only able to visualize the trends and make better decisions, using BigQuery eliminates the overhead of maintaining the underlying infrastructure or add more resources for servers/databases. The ability of using petabyte size data is pretty useful and is cost effective with pay per use features.

Pros

  • Serverless architecture is very useful as users do not have to maintain the underlying architecture
  • Fault tolerance and availability in multiple geographic regions means we can run the queries faster without data loss due to unforeseen circumstances
  • The real time cost estimator gives the data which can be processed and hence we are able to refine the queries and identify in advance what are we going to be charged
  • Ability to see job run history, project job run and see how much data is consumed by our queries including the efficiency and places for improvement in the project level

Cons

  • Any new feature introduced should have an information icon to see how much cost will be associated. Ex: Table Explorer feature recently caused some extra expenses in the project where even the preview feature led to additional costs
  • Ability to set billing quotas on individual accounts should be possible
  • With the advent of AI, BigQuery should also allow for asking questions in natural language and give output in the form of queries without high additional costs for this feature.

Likelihood to Recommend

We store GCP BigQuery to store long term data where personal information is redacted and another Splunk for checking day to day log or for troubleshooting by operations team. Since cost is associated with each query we have not found BigQuery to be useful in both of these use cases. In addition costs can quickly escalate when large datasets are involved. Similar use case is observable in transaction base data or data which needs to be frequently queried and the output is small in size, Minimum bytes charged is 10 MB.

Vetted Review
Google BigQuery
6 years of experience

Powerful GenAI powered Analytics and ML on Cloud. Google BigQuery

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

Google BigQuery is helping us with data preparation and storage. It is also helping with performing ML or Machine Learning operations natively. Support comes as Google BigQuery ML and AutoML which is easy to use and work with as the data is lies within Google BigQuery itself. The storage cost is pretty low for upto 1TB. There are multiple public data sets that helps build use cases easily.

Pros

  • Easily Create external tables on cloud storage based data.
  • Generate Auto ML for forecasting information
  • Query billions of rows easily and quickly at low costs.

Cons

  • It can expand the support for more ML algorithms
  • Lower the cost for the queries and simplify it by moving out from slot pricing to TB scans.
  • Add support for additional 3rd party data integration and ETL support.

Likelihood to Recommend

It is well suited for analytical and ML use cases on large data sets with ease. Enabling external data integration and allowing queries with various data sources without having to move the data to Google BigQuery, thereby saving cost and increased efficiency of the analysis being done. The Google BigQuery ML and AutoML integration has helped a lot by which the capability to create model, train, Forecast and evaluate can be done in the same platform or interface without having to leave the Google BigQuery environment. The capability to create visualizations via Google BigQuery on Looker Studio takes away the need for starting from scratch and helps immediate analysis of the data being rendered in the query.

Vetted Review
Google BigQuery
2 years of experience