Standard SQL calling legacy SQL usecase for external application to Big Query

Question

Say there is a table A that is a time-partitioned table. To reduce cost of queries, my organization created a view of B, which queries only last 3 days of data. This view B is described in legacy SQL. Next month, new applications will be connecting to BigQuery to read the B data via an ODBC connection? Below are couple of options of which, which could be the best option?

A - Creating a new view C over view B using standard SQL

B - Creating a new view over table A using standard SQL

You can't reference legacy SQL views from standard SQL queries. — Elliott Brossard
– Elliott Brossard, Commented Jan 23, 2019 at 4:14
Excellent. I just tested. I got this error - Cannot reference a legacy SQL view in a standard SQL query when tried. — Roshan Fernando
– Roshan Fernando, Commented Jan 23, 2019 at 5:37

Felipe Hoffa · Accepted Answer · 2019-01-23 08:22:18Z

2

B is the better option:

B - Creating a new view over table A using standard SQL

This because you can't call a #legacySQL view from a query using #standardSQL. So the best road will be to create a similar view, but this time with #standardSQL.

answered Jan 23, 2019 at 8:22

Felipe Hoffa

59.8k23 gold badges185 silver badges363 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Standard SQL calling legacy SQL usecase for external application to Big Query

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related