Bigquery Migration SQL Translator
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Data and AI
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The BigQuery Migration Service (BQMS) SQL Translator skill provides a structured approach for migrating legacy database dialects—including Teradata, Oracle, Redshift, Snowflake, SparkSQL, and HiveQL—to BigQuery GoogleSQL. It supports both interactive translation for single queries and batch translation for large-scale migrations. The skill manages the translation lifecycle, including staging files in Cloud Storage, configuring translation rules via YAML, and triaging compiler errors categorized by correctness, completeness, and compatibility.
What it does
- Translates SQL scripts, DDL schemas, and stored procedures to GoogleSQL.
- Supports batch migration of multiple files and metadata archives via Cloud Storage.
- Provides iterative workflows for resolving translation errors and warnings.
- Allows custom translation configurations using YAML for object renaming and schema redirection.
- Generates detailed translation reports to identify and track migration progress.
- Includes diagnostic tools to explain syntax differences and behavioral conversions.
When to use it
- When migrating legacy database workloads to BigQuery.
- When you need to convert proprietary SQL syntax or stored procedures to GoogleSQL.
- When performing large-scale batch migrations of SQL files and DDL schemas.
- When you need to apply specific translation rules or schema mappings during migration.
- When debugging translation errors in complex SQL queries.
Advantages
- Automates complex dialect-to-dialect syntax conversions.
- Resolves cross-file dependencies during batch migrations.
- Provides structured error reporting to guide manual remediation.
- Supports advanced configuration for fine-tuned translation control.
- Reduces manual effort in refactoring legacy database codebases.
Usage examples
- “Translate this Oracle SQL query to BigQuery GoogleSQL: SELECT * FROM employees WHERE rownum <= 10;”
- The agent uses the translate_query tool to convert the Oracle-specific rownum syntax into the equivalent BigQuery LIMIT clause, providing the translated SQL and any relevant logs.
- “I have a directory of Teradata SQL files in gs://my-bucket/input. How do I migrate them to BigQuery?”
- The agent initiates a batch translation workflow using translate_batch_queries, monitors the job status, and provides a summary report of the migration results.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/bigquery-migration-sql-translator/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip bigquery-migration-sql-translator.zip -d .agents/skills
Documentation by Google
BigQuery Migration Service (BQMS) SQL Translator
The BigQuery Migration Service (BQMS) translates legacy database SQL scripts, queries, and schemas into GoogleSQL. This skill coordinates translation workflows, Cloud Storage staging, compiler error triage, and YAML configuration.
Usage Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution.
Before you begin
Before translating queries or schemas, verify the following prerequisites:
Google Cloud SDK & Project Setup: Ensure the Google Cloud SDK is installed, verify that your Google Cloud project has an active Cloud Billing account attached, and select the target project:
gcloud config set project {project_id}Enable the API: Enable the BigQuery Migration API (
bigquerymigration.googleapis.com) in your Google Cloud project:gcloud services enable bigquerymigration.googleapis.comRequired IAM Roles: Verify that your identity or service account has:
roles/mcp.toolUser(MCP Tool User)roles/bigquerymigration.editor(Migration Workflow Editor)For batch translation,
roles/storage.objectViewerandroles/storage.objectCreator(orroles/storage.objectAdmin) on the Cloud Storage buckets that hold the input and output files.
MCP Server Connection: If BigQuery Migration Service (BQMS) tools (e.g.
translate_query,translate_batch_queries) are not present in your active tool list, configure the remote BigQuery Migration Service (BQMS) MCP server. For setup instructions across clients (Claude, Cursor, Gemini CLI, VS Code), see mcp_config.md.Cost & Cloud Storage Cleanup: Review Google Cloud Pricing for Cloud Storage and BigQuery usage details. After completing a batch migration, clean up temporary staged input and output folders in Cloud Storage:
gcloud storage rm -r gs://{bucket}/{folder}Translation Tracking: For batch translations, and for queries that need more than one translation iteration, keep a translation tracker (e.g.
translation_tracker.md) to document goals, planned steps, and progress. After each translation, record one row with this template:Iteration Status Total Errors Correctness Errors Completeness Errors Compatibility Errors Key Actions / Transformations A single query that translates cleanly on the first attempt needs no tracker: report its translation ID and logs in your response.
Workflow Selection
Choose the workflow based on your migration scope:
Interactive Translation (Single Query): Best for ad-hoc queries, exploratory testing, dialect syntax comparison, or quick error debugging.
Batch Translation (Multiple Files & Cloud Storage): Use for more than one file or a directory, including SQL embedded in application code (extract it into
.sqlfiles first). For multi-file Python codebases containing embedded SQL, use python_embedded_sql_migrator_template.py to extract queries into staged files and re-inject translated SQL. Batch translation is faster and cheaper than translating files one by one, and it resolves cross-file dependencies, so it usually gives better results. Runtranslate_batch_querieson the staged files first; usetranslate_queryonly afterwards if needed to debug a specific statement fromtranslation_report.csv.
1. Interactive Translation Workflow
Use the interactive workflow to translate a single query string, inspect compiler logs, and iteratively resolve issues.
Steps
Submit Query (
translate_query): Calltranslate_querywithprojectNumber,location,inputQuery,sourceDialect, andtargetDialect(BigQuery). Include optional parameters:metadataFilePath: Cloud Storage URI to a metadata zip file (gs://.../metadata.zip) for schema resolution.translationConfigs: Inline YAML configurations (e.g. object renaming, schema redirection, optimizer rules). Show the YAML you used in your response so the user can reuse it (e.g. in batch translation).
Poll Status (
get_translation): If the returnedtranslation_stateisRUNNINGorPENDING, pollget_translationusing thetranslationID,projectNumber, andlocationuntiltranslation.stateisSUCCEEDEDorFAILED, at the interval given in the BigQuery Migration Service (BQMS) MCP tool descriptions. While the job runs, do work that doesn't need the result (e.g. read the dialect gotchas reference).Inspect Output & Logs:
Examine
translated_queryfor the converted GoogleSQL.Review each entry in
translation_logs: inspectseverity(ERROR,WARNING),category(e.g.RelationNotFound), andeffect(CORRECTNESS,COMPLETENESS,COMPATIBILITY).Check the SQL itself, not only the logs: BigQuery Migration Service (BQMS) emits
ERROR_TYPE(...)for types it cannot map, sometimes with no log entry. Treat anyERROR_TYPEor inline error comment as an error, and when a BigQuery project is available, dry-run the result (bq query --dry_run --use_legacy_sql=false). ANot foundormust be qualified with a dataseterror still means the SQL is syntactically valid; the referenced objects just don't exist in BigQuery yet. Say so and move on, even if the error suggests a fix: don't stub tables or change the SQL orbqflags to get past it.A
NoSuchFunctionerror means BigQuery Migration Service (BQMS) copied that call unchanged, sometimes with the function name in backticks. Treat it as untranslated even if BigQuery has a function with that name: a dry run that stops at missing tables doesn't check it.If the source dialect has a gotchas reference (see Dialect-Specific Gotchas), read it and check the output for the patterns it lists. Some semantic differences produce no log entry and still pass a dry run.
Iterate Until Clean: If the logs contain errors or warnings, the translated SQL contains
ERROR_TYPEor inline error comments, the dry run fails, or the output matches a dialect gotcha, resolve the issues as described in Resolving Translation Issues and re-translate.Explain & Compare Differences (
explain_translation): When requested to explain a translation, compare syntax differences, or understand how specific query logic was converted, callexplain_translationwithtranslation(the translation ID),projectNumber, andlocation. This returns a structured explanation of the query's purpose and a detailed breakdown of syntax, function, and behavioral differences between the source query and the translated GoogleSQL. The explanation doesn't validate the output, so check the translation as in step 3 rather than relying on it.
2. Batch Translation Workflow
Batch translation handles multiple files staged in Cloud Storage. It resolves
cross-file dependencies and produces a consolidated translation summary report
(translation_report.csv).
Steps
Stage Input Files to Cloud Storage: Upload the raw SQL files, configuration files (
*.config.yaml), and any metadata file from the local workspace to a Cloud Storage input folder:gcloud storage cp input/*.sql gs://my-bucket/migration/input/ gcloud storage cp *.config.yaml gs://my-bucket/migration/input/Note: Do not pass configuration file paths in tool parameters if those files are already located inside
sourceBaseUri.Use new, empty Cloud Storage input and output folders for each run (e.g. with a timestamp suffix). Stage only files from the local workspace or generated in this run. Never reuse or copy inputs, DDL, or outputs that are already in a bucket from earlier runs: they may come from different inputs or settings.
Initiate Batch Translation:
Translating SQL Queries (
translate_batch_queries): Calltranslate_batch_querieswithprojectNumber,location,sourceDialect,targetDialect,sourceBaseUri, andtargetBaseUri.Translating Metadata Zip Files (
translate_metadata): To aid batch translation by generating target BigQuery DDL schema definitions from an extracted database metadata zip file (metadata.zipfrom Teradata, Oracle, etc.), calltranslate_metadataspecifyingsourceBaseUri(Cloud Storage URI tometadata.zip) andtargetBaseUri(destination Cloud Storage folder).
Poll Completion (
fetch_batch_translation): Poll using the returned workflow ID untiltranslation.stateisSUCCEEDEDorFAILED, at the interval given in the BigQuery Migration Service (BQMS) MCP tool descriptions.Retrieve & Inspect Outputs: Download the generated files from
translation.target_base_uri:gcloud storage cp -r gs://my-bucket/migration/output/ ./local_output/Locate and inspect
report/translation_report.csvto review all warnings, errors, and line-level diagnostics. Then scan the generated.sqlfiles forERROR_TYPE(...)and inline error comments, which the report can miss, and dry-run the generated SQL when a BigQuery project is available (handleNot founderrors as in the interactive workflow). Check the output for the patterns in the source dialect's gotchas reference, if one exists. Resolve or clearly report every remaining issue; do not describe the output as clean until this check passes.Iterate Until Clean: Resolve the issues found in step 4 as described in Resolving Translation Issues, and re-run from step 1 with the changed inputs.
Post-processing (Final Step Only): Only after resolving every compiler error that re-translation can fix, execute any application-level post-processing (e.g. AST re-injection) to restore host source files. effect_correctness.md lists the errors that may remain when re-injecting embedded SQL.
Resolving Translation Issues
Both workflows resolve issues the same way:
Identify the Effect (
CORRECTNESS,COMPLETENESS,COMPATIBILITY) of each issue, and resolve them in order of compiler phase dependencies:CORRECTNESS(parse errors) first, thenCOMPLETENESS(missing objects), thenCOMPATIBILITY(unsupported features).MUST Read the Reference Guide for each effect in Troubleshooting by Error Effect BEFORE applying fixes, and follow its resolution workflow.
Fixes can preprocess the input (e.g. prepend DDL) or post-process the BigQuery Migration Service (BQMS) output (e.g. a rewrite that a dialect gotcha calls for). Run BigQuery Migration Service (BQMS) on the preprocessed input rather than translating it yourself.
Keep the source system's dialect for every re-translation. Another dialect may accept the same SQL but translate it with different semantics (e.g. return types, numeric types, or identifier case), so don't switch dialects to get cleaner output.
Rewrites of the BigQuery Migration Service (BQMS) output, including optimizations the user asks for, must return the same rows as the source query. For example, a filter that runs after a row limit (
TOP,LIMIT) can't be merged into the query before the limit.Wait for each re-translation to finish, record its translation ID, error counts, and any pre- or post-processing in the tracker, and compare the counts with the previous iteration. Repeat until no errors remain or all options are exhausted.
Report the final SQL from the tracked iteration, the pre- and post-processing you applied, and any errors that remain.
Reference Lookup Index
Use these reference guides when troubleshooting errors or authoring configuration files:
Troubleshooting by Error Effect
| Effect | Common Causes | Reference Guide |
|---|---|---|
CORRECTNESS | Syntax errors, unescaped literals, application script wrappers, NoSuchFunction. | effect_correctness.md |
COMPLETENESS | Missing tables, views, columns (RelationNotFound, AttributeNotFound), DDL suggestions. | effect_completeness.md |
COMPATIBILITY | Functions or features without direct GoogleSQL mapping. | effect_compatibility.md |
Configuration & Setup Guides
| Task | Description | Reference Guide |
|---|---|---|
| YAML Configurations | Database/schema redirection, name mapping, table partitioning and clustering injection, optimizer transformations, statement rewriters, and environment settings. Schemas in assets/translation_config_schemas/ and examples in assets/translation_config_examples/. | translation_yaml_config.md |
| MCP Server Setup | Configuring the remote BigQuery Migration Service (BQMS) MCP server, OAuth scopes, and IAM roles. | mcp_config.md |
Dialect-Specific Gotchas
| Dialect | Key Considerations | Reference Guide |
|---|---|---|
| Teradata | SET/MULTISET tables, SAMPLE clause, primary index mapping. | teradata_gotchas.md |
| Oracle | PL/SQL procedures, ROWNUM emulation, outer join (+), sequences. | oracle_gotchas.md |
| Snowflake | Dynamic templates, USE statements, metadata merging, lateral joins. | snowflake_gotchas.md |
Files
- ATTRIBUTION.mdAdded by AutoGineer884 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md16.0 KiB
- assets/python_embedded_sql_migrator_template.pyScript41.8 KiB
- assets/translation_config_examples/environment_example.yaml167 B
- assets/translation_config_examples/experimental_input_formats_example.yaml213 B
- assets/translation_config_examples/experimental_metadata_example.yaml147 B
- assets/translation_config_examples/experimental_object_rewriter_example.yaml1.5 KiB
- assets/translation_config_examples/experimental_optimizer_example.yaml348 B
- assets/translation_config_examples/experimental_statement_rewriter_example.yaml400 B
- assets/translation_config_examples/input_formats_example.yaml200 B
- assets/translation_config_examples/metadata_example.yaml168 B
- assets/translation_config_examples/object_rewriter_example.yaml673 B
- assets/translation_config_examples/optimizer_example.yaml335 B
- assets/translation_config_examples/statement_rewriter_example.yaml387 B
- assets/translation_config_schemas/environment.json498 B
- assets/translation_config_schemas/experimental_input_formats.json976 B
- assets/translation_config_schemas/experimental_metadata.json629 B
- assets/translation_config_schemas/experimental_object_rewriter.json19.5 KiB
- assets/translation_config_schemas/experimental_optimizer.json635 B
- assets/translation_config_schemas/experimental_statement_rewriter.json1.3 KiB
- assets/translation_config_schemas/input_formats.json963 B
- assets/translation_config_schemas/metadata.json876 B
- assets/translation_config_schemas/object_rewriter.json9.2 KiB
- assets/translation_config_schemas/optimizer.json622 B
- assets/translation_config_schemas/statement_rewriter.json1.2 KiB
- assets/translation_config_schemas/transpiler_config_spec.json38.9 KiB
- references/attribution.md1.9 KiB
- references/effect_compatibility.md2.3 KiB
- references/effect_completeness.md5.1 KiB
- references/effect_correctness.md8.6 KiB
- references/mcp_config.md10.0 KiB
- references/oracle_gotchas.md3.1 KiB
- references/snowflake_gotchas.md7.4 KiB
- references/teradata_gotchas.md2.4 KiB
- references/translation_yaml_config.md12.3 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs a command-line tool, Needs Python
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/bigquery-migration-sql-translator · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download bigquery-migration-sql-translator.zip