| Hello 勇汀, If you are not familiar with legacy SQL or do not consider it relevant to your workflow, please disregard this message. We're writing to inform you that, after June 1, 2026, the legacy SQL dialect in BigQuery will transition to a restricted availability mode in your organization/projects. Your organization/projects have not used legacy SQL since at least November 1, 2025, so we don't expect them to be affected by this change. What's changing? After June 1, 2026, any queries written in legacy SQL will fail when run in your existing organization/projects or any new organizations. If you have queries that use legacy SQL, please follow the migration guide to rewrite your queries using GoogleSQL. What you need to do Our records show that your organization/projects listed in the attachment provided have not executed any legacy SQL queries since at least November 1, 2025. Based on this finding, no action is required from you, as this change will not affect your workloads. If you believe you need to continue to have access to legacy SQL, please refer to Legacy SQL feature availability for more details. Why are we making this change? Since 2016, GoogleSQL has been the default, ANSI-compliant standard. We recommend using it over legacy SQL for the following operational reasons: - Standardization: It aligns with ANSI SQL standards
- Maintenance: It receives all current updates and new system functions
- Efficiency: It is a more cost effective option
Please refer to our migration guide for a technical comparison of the two dialects. We're here to help If you have any questions, please don't hesitate to reach out to Google Cloud Support for help. Thank you for choosing BigQuery. | 
