Google BigQuery: Self-service cloud data analysis, from your iPad or desktop

Google BigQuery: Self-service cloud data analysis, from your iPad or desktop

Summary: Google made its BigQuery service publicly available last month. So I decided to put it through its paces, and compare it to Microsoft’s Excel and PowerPivot.

SHARE:

 |  Image 2 of 11

  • Thumbnail 1
  • Thumbnail 2
  • Thumbnail 3
  • Thumbnail 4
  • Thumbnail 5
  • Thumbnail 6
  • Thumbnail 7
  • Thumbnail 8
  • Thumbnail 9
  • Thumbnail 10
  • Thumbnail 11
  • Google made its BigQuery service public on May 1st.  Though the name sounds like “Big Data,” Google’s offering is really a self-service Business Intelligence (BI) solution, hosted in the cloud.  In this gallery, I'll tell you how it works.

    BigQuery is a cloud-based data analytics system from Google.  It lets you upload data, then analyze it using SQL (Structured Query Language) as the query interface.  BigQuery lets you query up to 100GB of data per month for free.  Just create a Google Developer account for yourself, create a new project and enable BigQuery within it.

    Click on any image to enlarge.

    Source: Google

  • BigQuery offers a simple, easy to master browser console, providing for dataset browsing on the left and SQL querying on the right.  When queries are returned, options appear to let you save the results in alocal CSV file or create a new table containing the result set’s content.

    A simple query against the sample github_timeline table is shown here.  The first few rows from the results of the query appear on the bottom-right of the screen, along with navigation controls that allow you to page through the data.  Note the “Save as Table” and “Download as CSV” options, which work nicely in Chrome and FireFox.  Unfortunately, the "Save as Table" option is not available in Internet Explorer (nor is a file upload option we'll look at shortly).  Everything in BigQuery also works nicely in Safari on the iPad, though you can’t save or upload local files there either.

  • BigQuery data is stored in tables, much as in a relational database.  Tables, in turn, are stored within datasets.  Datasets serve as a unit of security, allowing for sharing with specific users or the overall public.  Google supplies the publicdata:samples dataset which is added to every BigQuery project.  This allows you to examine and query tables right away.

    At the left side of the screen, you can drill down on a dataset to see the tables it contains.  Select one of those tables and its schema will appear on the right-hand side of the console.  The github_timeline table’s schema is displayed in this figure.  Notice that its label on the left side of the screen appears in bold text with a red bar beside it.  The “Click to preview table data” link does what it says, but you can also write your own SQL queries.
     

Topic: Enterprise Software

Andrew Brust

About Andrew Brust

Andrew J. Brust has worked in the software industry for 25 years as a developer, consultant, entrepreneur and CTO, specializing in application development, databases and business intelligence technology.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

Talkback

3 comments
Log in or register to join the discussion
  • Data privacy?

    BigQuery provides big-data analytics in a completely hosted offering. Hope there is no issue on the front of data privacy. Any idea?

    - Lisa
    http://www.hireamobileappdeveloper.com/
    SaraParker23
  • BigQuery or PowerPivot

    What exactly was this article about?

    So I can load data into BigQuery using CSV, export it out as CSV, import the CSV into Excel, then use PowerPivot to actually do analytics.

    Why not just go from CSV directly into Excel? What value is BigQuery bringing to the process; other than turning over my data to Google and giving me a query interface (but not a visualization interface) that will work on an iPad?
    Marc Jellinek
    • PowerPivot or BigQuery

      @Mark, my goal was to show you how BigQuery works, and to contrast that with how you might do similar work in Excel. I wasn't suggesting that you use one and then move the output to the other, although that would work.

      When you ask "Why not just go from CSV directly into Excel?", I suppose that is one of the questions I wanted to provoke you to think about. Would you rather use something like PowerPivot + Excel on your desktop, or would you prefer to stay cloud + browser (and SQL) based and use BigQuery? What's your take? Does the cloud trump the desktop + Excel?
      andrewbrust