Converting SQL¶
Converting SQL is turning source-platform DDL, views, procedures, functions, and scripts into Snowflake SQL (and the matching Snowflake objects) so you can deploy and test on Snowflake. The Snowflake AIM Agent for Data Warehouses drives this conversion: it runs deterministic translation first, then layers AI-assisted remediation, assessment, and deployment.
SQL conversion in the Snowflake AIM Agent for Data Warehouses¶
The agent treats SQL conversion as a defined stage after your source is registered in the project, with deterministic translation as the baseline and AI as the remediation layer:
| Capability | What it means |
|---|---|
| Register code units | Pull DDL and procedural code from a live SQL Server or Redshift connection, or import existing .sql files into the project |
| Convert code | Translate source SQL (for example T-SQL or Redshift SQL) into Snowflake-compatible SQL, with a per-object summary plus an EWI report (errors, warnings, informational issues) |
| AI-assisted conversion | After the deterministic pass, AI explains remaining EWIs, suggests fixes, and applies them interactively against the same converted code |
| Rule engine | Capture recurring fixes as reusable rules (regex or AI-guided) and propagate them across many files when the same EWI repeats |
The conversion stage feeds directly into Stage 6 (Migrate), where deploy, data copy, testing, and iterative fix loops continue.
Example prompts (from the skill topic):
Use "What is the current state?" at any time to reopen the progress checklist.
Platform availability for code extraction, deterministic conversion, AI conversion and verification, and deploy appears in the Supported source systems table in the Snowflake AIM Agent for Data Warehouses (deterministic conversion is available across SQL Server, Redshift, Teradata, Oracle, and other dialects today; extraction, AI verification, and deploy currently target SQL Server and Redshift, with additional sources on the roadmap).