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 Migration Agent covers reporting today through Power BI repointing, on top of SnowConvert AI’s repointing engine and the dialect-specific BI repointing references documented elsewhere in this tree.
Reporting in the Snowflake Migration Agent¶
The skill 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 Migration Agent (supported across SQL Server, Redshift, Teradata, and Oracle today; Synapse and PostgreSQL are limited to a subset of repointing scenarios).
If you want to explore further, the SnowConvert AI documentation for Power BI repointing is where you will find fuller answers on architecture and how to use the products: how the tool consumes .pbit files, what it rewrites inside the M Language and Snowflake connector, the parameters it injects (SF_SERVER_LINK, SF_DB_NAME, SF_WAREHOUSE_NAME), the ETLAndBiRepointing report it produces, and the supported / unsupported connector scenarios.
SnowConvert AI: Power BI repointing is the place to start for the end-to-end repointing flow. Dialect-specific repointing references live under ETL and BI repointing in the translation references — for example Power BI (SQL Server / Synapse), Power BI (Oracle), Power BI (Teradata), Power BI (Redshift), and Power BI (PostgreSQL).