|
Hello vv,
We’re writing to remind you that starting August 1, 2025, GoogleSQL will become the default dialect for queries. If you wish to continue using LegacySQL, you will need to explicitly specify it in your requests.
If you do not intend to use the LegacySQL dialect, this change does not affect you.
We have provided additional information below to guide you through this change.
What you need to know
Key changes:
The change applies only to queries sent through a BigQuery command line interface or directly through BigQuery API. In the Google Cloud console, BigQuery API client libraries, and Google JDBC/ODBC drivers, we already treat GoogleSQL as the default dialect.
GoogleSQL was introduced nine years ago and we keep innovating on its capabilities and performance. Therefore, we recommend it for all new use cases.
What you need to do
Required actions:
If you would like to use LegacySQL, here are your options:
- Specify it per-query, using the useLegacySql flag,
- Set the configuration setting 'default_sql_dialect_option' to ‘default_legacy_sql’ at the project or organization level.
Timeline and potential impact:
If you do not take action by August 1, 2025, your queries (in the CLI and API) will be interpreted as GoogleSQL by default, and they may start failing if they use LegacySQL syntax that is unsupported in GoogleSQL.
If you want to list any jobs that are using LegacySQL, you can query the ‘query_dialect’ column from the INFORMATION_SCHEMA.JOBS view.
We’re here to help
We understand that these changes might require you to make some adjustments. If you have any questions or require assistance, please contact Google Cloud Support.
Thanks for choosing Google BigQuery.
|
Comments
Post a Comment