Reporting¶
Reporting in a Snowflake migration is the work of pointing BI tools and analytics consumers at Snowflake after your database and pipelines have moved. In practice, this means repointing existing reports — updating their data sources, embedded SQL, and parameters — so dashboards and ad hoc queries run against Snowflake instead of the legacy platform. The Snowflake AIM Agent for Data Warehouses covers reporting today through Power BI repointing.
Reporting in the Snowflake AIM Agent for Data Warehouses¶
The agent exposes report repointing as a defined capability that uses the same migration context as code conversion, so embedded SQL is rewritten in line with the rest of the migration:
| Capability | What it means |
|---|---|
| Repoint reports | Repoint Power BI reports so Snowflake is the data source after database migration |
| Migration-aware rewriting | Embedded SQL queries inside reports are translated using the same migration context (object renames, schema mapping, dialect rules) as the rest of the project |
| Output structure | Repointed reports land under Output/repointing_output/, with extracted source SQL preserved under power_bi_sql_queries/ for review |
Repointing currently expects Power BI reports in .pbit (template) format; .pbix files must be saved as .pbit before they are added to the project.
Example prompt (from the skill topic):
Platform availability for Power BI report repointing appears in the Supported source systems table in the Snowflake AIM Agent for Data Warehouses (supported across SQL Server, Redshift, Teradata, and Oracle today; Synapse and PostgreSQL are limited to a subset of repointing scenarios).