Google's BigQuery is part of the Google Cloud Platform, a database-as-a-service (DBaaS) supporting the querying and rapid analysis of enterprise data.
$0.04
Looker
Score 8.7 out of 10
N/A
Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
N/A
Pricing
Google BigQuery
Looker
Editions & Modules
Standard edition
$0.04 / slot hour
Enterprise edition
$0.06 / slot hour
Enterprise Plus edition
$0.10 / slot hour
No answers on this topic
Offerings
Pricing Offerings
Google BigQuery
Looker
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
Must contact sales team for pricing.
More Pricing Information
Community Pulse
Google BigQuery
Looker
Considered Both Products
Google BigQuery
Verified User
Anonymous
Chose Google BigQuery
It's easier to connect data between BigQuery and looker studio instead of connecting the data between BigQuery and tableau in terms of data explore or dashboard creating. Therefore we are considering migrating dashboards from tableau to looker studio for the whole company. On …
I personally find it by far simpler than Amazon redshift due it's onboarding seamlessness. For a quick start and simplify tye access to read the data big query provide better user experience and a smoother user interface. More importantly, the fact that Big Query can be easily …
is much better as it’s easily accessible provides velvet documentation and fulfils all our needs as well as easily integrated into clients, environment
Google BigQuery is simpler and I say it has simpler UI too. If you have a clear long term ask , mainly business intelligence needs then Google BigQuery offers you good. If you need too much of features under a single cloud and you are ok to be lil clumsy then you can check …
I have used most of the data analytics platforms. Based on my work, I have found that the user interface of Google BigQuery is simple to navigate. I like the front view - ease of joining tables, and integration with other platforms.
Compared to every other analytics DB solution I've used, Google BigQuery was by far the easiest to set up and maintain, and scale. The price was also much lower for our use case (internal data analysis).
For our usage, Google BigQuery is cheaper and more performant. The others have their place, but in certain scenarios, Google BigQuery is a better solution.
We actually use Snowflake and BigQuery in tandem because they both currently meet various needs. Redshift, however, has barely been used since our migration away from it. In the case of both Snowflake and BigQuery, they beat Redshift by a long shot. The main reasons are their …
I came to use BigQuery from a traditional system like MS SQL server, the features which are available in BigQuery as a cloud service far outweigh the features from SQL server. I have not used other similar tools like Amazon Redshift but Google BigQuery serves multiple use cases …
Google BigQuery is cheaper and much faster as compared to both. While as compared to Snowflake , we tested it was faster and cheaper by 30%, that is after Snowflake tweaked their environment, if not for that it would have been 90% cheaper than snowflake. Redshift is not easy …
In my opinion, Google BigQuery is custom made to be the best data lake system that is easy to use, scalas to fit any business size, has inbuilt security, as well as tools for data integrity. Although a few other tools have some of the same functionality, Google BigQuery is the …
When comparing Google BigQuery and Databricks, both platforms are powerful tools for managing and analyzing large datasets. BQ is ideal for businesses requiring large-scale analytics, reporting, and dashboarding with minimal operational overhead. It’s also great for ad-hoc …
Google BigQuery's main advantage over its direct competitors (Amazon Redshift and Azure Synapse) is that it is widely supported by non-Google software, while the others rely heavily on their own cloud ecosystems.
I have used other data manipulation tools like SQL Server and Google BigQuery feels more intuitive, Google provides so much documentation and tutorials that getting to know the software is not only easy but even satisfactory, so I'd say Google BigQuery is very superior to that …
Amazon Redshift was a likely alternative we were considering , but it needs to be provisioned on cluster and nodes, which increases infrastructure management, whereas Google BigQuery is serverless, so no infra management :) Also, I remember when comparing them we did found out …
Google BigQuery as a platform allows for more integrations and customizability than many other offerings. Users mostly need to understand the basics of database and SQL programming in order to get the most from the product. However, other products like Hevo do have less of a …
There are some areas in which this product is better while there are some in which others do better. It's not like Google BigQuery surpasses them in every metric. For a holistic view, I will say we use this because of - scalability, performance, ease of use, and seamless …
The data performance of Google BigQuery is best as per other software. Limitations on Google BigQuery's data size are superior to those of Microsoft SQL. Obtaining real-time data from several IoT devices is another benefit.
BigQuery can automatically scale to accommodate the data and query load, providing potentially unlimited scalability. At the same time, Redshift requires manual scaling efforts to increase or decrease capacity, which might affect performance during scaling operations.
We focused more on data volume and less on full application capabilities. All in all, we found that the two solutions complement each other. For integration, some sources were better handled in SAP HANA, particularly other SAP systems where Google Big Query was more suitable …
SingleStore has a much lower query latency compared to BigQuery. Thus, we segregate faster tasks to SingleStore, and use BigQuery has our main database to store all historical data.
Google BigQuery i would say is better to use than AWS Redshift but not SQL products but this could be due to being more experience in Microsoft and AWS products. It would be really nice if it could use standard SQL server coding rather than having to learn another dialect of …
First and foremost, Google BigQuery's pricing structure, based on data processing and storage, is more cost-effective for our needs. Secondly, since we already use other Google Cloud services, its tight integration with them especially, with Cloud Storage and Dataflow was a big …
Better in terms of data configuration with slight harder learning curve, available help material is not that much and we usually have to connect with Looker Help with chat for our data and analysis questions. While Looker offers a wide range of visualization options, there were …
It takes forever sometimes to have data ready in tableau dashboard, and also it takes effort to maintain each dashboards. We do not have so many efforts to maintain all. Also, we need to be able to see data faster and therefore take actions and work faster. With Looker we might …
Looker Studio is not as robust as Tableau or Microsoft BI. So it does not provide quite as much insight or depth and it has more limitations overall then the other major reporting products. However, it is also free and connects perfectly with other Google products. Plus, all of …
Technically, Power BI is much more complete and powerful, but it's like an ocean liner. I didn't need all that equipment. In my case, I needed to move more quickly, like on a speedboat, to build a page with several data sources in a single source of truth that could be easily …
Looker is a free tool to use on the basic level, which can't really compare apples to apples since all of the other services are paid services. Looker already has a leg up because of that. The other platforms definitely have more features and capabilities off the bat because it …
The learning curve for Tableau Cloud was too steep for our team. After watching a couple of YouTube videos, anyone can begin connecting data sources and creating reports with Looker. Looker is also free with Google Workspace, making the decision between Looker and Tableau a …
Tableau did not have the customization that we were told it had, and it was expensive. Domo looks promising, but is also expensive so we haven't purchased it (we may in the future). Google Sheets was very basic and did fine for what it was, but we needed something a bit more …
Looker seems to be all inclusive in data analysis and reporting. Along with the ability to forecast and add specific metrics to data sets. The automatic reporting sending them on scheduled days is great as well. The only concern is the ease of use as it requires high level …
I have not used any other products like Looker before and the company has been using Looker since I've joined. We've talked about replacing other software vendors in the past but never discussed replacing Looker because of how vital it is to our organization.
Looker is a great fit for our company because we have collaborative analytics workflows and complicated data ecosystems and because of its strengths in data modeling, integration, and collaboration. Brand name and peer recommendations also helps us to select Looker against …
Our organization is going all in on Google products so switching out of the Microsoft suite of tools is a no brainer. All the Google tools work incredibly well together and once you transition it’s incredibly hard to be half in half out between Google and Microsoft. If you’re a …
Looker is more mailable; it allows more dynamic visualisations, filters, drilldowns etc. It's sharing capabilities are also more streamlined than AWS Quicksight. However in contrast to this AWS Quicksight can leverage AWS IAM roles and policies which can be quite scalable. …
Looker is free, so it's certainly better bang for your buck. It's a good platform for someone who just needs a quick way to look at the data they have. It doesn't have some of the advanced functionality that Tableau has, but it integrates well with the Google ecosystem, so it's …
In terms of reporting specifically Looker Studio allows to integrate way more sources into a single report. If needed sources can be blended and parameters can be created with calculations etc
We haven't had a proper benchmarking done. We might consider looking at other options, but this thing is deeply integrated into our platform, so not anytime soon.
I choose Looker when I need quick charts. It is easier to start and configure, browser-based, and easy to connect with Google Sheets. This gives it a good competitive advantage when comparing pricing—other similar tools have expensive licenses. In a corporate Google …
Looker and Tableau are similar products with benefits and drawbacks according to which software you choose to employ. Looker is a Google product whereas Tableau is a Salesforce product. Depending on your existing tech stack it is recommended to leverage the integrated, native …
Looker is web based app and much easier to use.¨ON the othe hand Power BI offers robust integration with Microsoft products (like Azure, SQL Server, and Excel) and a wide range of other data sources. Power BI's ability to seamlessly connect and import data from these sources is …
We use both Looker and Tableau. It depends on the specific team. However, there is a clear correlation that we use Tableau more often when there are more data sources, including financial data.
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.
When you need to create a centralised dashboard for multiple stakeholders that blends cross-channel reporting. As an SEO agency reporting for clients - Looker is a great solution. It's less appropriate depending on the intended users. For instance, in my experience Looker reports have been under-utilised because they're not accessed regularly, provide too much noise or often simple PDF reports are preferred
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.
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.
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.
We are very haooy with Looker, it provides us with all the funciomalities we need for both the day to day oerformance tracking and longer periods reporting. It is easy to use for account managers, configurable and customizable for soecialists and what is most imoortant, our clinets generally really love it
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
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
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.
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.
Somehow resources heavy, both on server and client. I recommned at least 50Mbs data rate and high performance desktop comouter to be abke to run comolex tasks and configure larger amount of data. On the other hand, the client does not need to worry when viewing, the performance is usually ok
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.
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
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.
In my opinion, Looker is no Power BI. It is good, but I think Power BI is amazing. That said, in my experience, Power BI is nowhere near as easy to setup and report on Google services as Looker is. We plan to continue using Power BI for c-suite and corporate reporting, especially for internal databases, but will gladly use Looker for our marketing information for AdWords, Analytics, Search Console, and YouTube.
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.
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.
Other than some people not liking the numbers, I don't see any negative impacts; we haven't experienced that.
The reports help us unravel the story of our users and how they are sifting through our pages.
Our clients enjoy seeing the numbers to understand better what stands out on their sites.
The reports have helped us see what campaigns are working and where we need to tweak things.
The reports have enabled us to have better conversations with stakeholders about how their web pages should be modified, edited, etc., to reflect the data.