Troubleshooting Common SQL Errors with BigQuery v1.5 Reviews

Nataliia R. · Reviewed almost 2 years ago

Hugo C. · Reviewed almost 2 years ago

Bartosz C. · Reviewed almost 2 years ago

Some of the questions were vague or open to interpretation.

LaVar E. · Reviewed almost 2 years ago

Yusuf D. · Reviewed almost 2 years ago

Bhagavan Reddy E. · Reviewed almost 2 years ago

MURALI K. · Reviewed almost 2 years ago

Ghazal R. · Reviewed almost 2 years ago

Fatih G. · Reviewed almost 2 years ago

T S. · Reviewed almost 2 years ago

Aniket P. · Reviewed almost 2 years ago

Annie B. · Reviewed almost 2 years ago

Ravi L. · Reviewed almost 2 years ago

Useful

Gurusam N. · Reviewed almost 2 years ago

Alfie F. · Reviewed almost 2 years ago

Andreea G. · Reviewed almost 2 years ago

Paul M. · Reviewed almost 2 years ago

chikkondu v. · Reviewed almost 2 years ago

Anthony P. · Reviewed almost 2 years ago

Jorge G. · Reviewed almost 2 years ago

Jessica Y. · Reviewed almost 2 years ago

One question assumes the user has seen Legacy SQL before, and would know how to identify it. If a person is inexperienced enough to need this lab, what are the chances they have history with Legacy SQL? One question expects you to answer that "page title" is missing from the query, when "page title" was never specified in the requirements for the query. One question expects you to answer "Large GROUP BYs hurt performance..." but the table only has ~56k records. 56k records meets google's definition of "large?" One question asks you to identify a logical problem with a query, without first defining what the query is supposed to do. From a pedagogical standpoint, this is a terrible lab.

Kurtis C. · Reviewed almost 2 years ago

Matias Ezequiel P. · Reviewed almost 2 years ago

Nguyen Duc Dung H. · Reviewed almost 2 years ago

Nice

EDWIN O. · Reviewed almost 2 years ago