Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Google Cloud Platform for Architects

You're reading from   Google Cloud Platform for Architects Design and manage powerful cloud solutions

Arrow left icon
Product type Paperback
Published in Jun 2018
Publisher Packt
ISBN-13 9781788834308
Length 372 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
Loonycorn Ravi Loonycorn Ravi
Author Profile Icon Loonycorn Ravi
Loonycorn Ravi
Judy Raj Judy Raj
Author Profile Icon Judy Raj
Judy Raj
Vitthal Srinivasan Vitthal Srinivasan
Author Profile Icon Vitthal Srinivasan
Vitthal Srinivasan
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. The Case for Cloud Computing FREE CHAPTER 2. Introduction to Google Cloud Platform 3. Compute Choices – VMs and the Google Compute Engine 4. GKE, App Engine, and Cloud Functions 5. Google Cloud Storage – Fishing in a Bucket 6. Relational Databases 7. NoSQL Databases 8. BigQuery 9. Identity and Access Management 10. Managing Hadoop with Dataproc 11. Load Balancing 12. Networking in GCP 13. Logging and Monitoring 14. Infrastructure Automation 15. Security on the GCP 16. Pricing Considerations 17. Effective Use of the GCP 18. Other Books You May Enjoy

Legacy versus standard SQL

BigQuery, like many other GCP services, has been widely used within Google for several years. That usage initially relied on a non-standard variant of SQL, which is now called legacy SQL. Legacy SQL is pretty powerful and pretty easy to use in some specific cases, but it has a big downside: it is not standard!

To remedy that, BigQuery has added support for standard SQL 2011, with some extensions that have to do with nested and repeated fields. The query examples shown next are in standard SQL.

How can you tell at a glance whether a query is written in legacy SQL or standard SQL? Just look at the syntax used to specify tables or project names.

  • In legacy SQL: Use square brackets to start and end the table name, and use a colon (:) to delimit dataset and table names:
[bigquery-public-data:samples:natality]
  • In standard SQL: Use the backtick character...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image