Forum Discussion
Helper IIHow to migrate SQL views, and Power BI reports from UAT to Production?
Hi everyone,
I developed several Power BI reports in a Microsoft Fabric for D365 F&o UAT environment.
These reports use a Lakehouse as the data source.
Inside the Lakehouse SQL endpoint, I created SQL views, and my Power BI models connect to those views.
Everything works perfectly in UAT.
Now I want to move the entire setup to Production, including:
SQL views
Power BI datasets
Power BI reports
I’m not sure what is the correct / recommended approach for migrating all of these.
My questions:
Do SQL views need to be recreated manually in the Production SQL endpoint, or is there a migration tool?
How do I repoint my Power BI datasets to the Production Lakehouse views without rebuilding everything?
Is there a deployment pipeline or workspace-to-workspace migration approach for Fabric Lakehouse + Power BI together?
Any step-by-step guidance or recommended strategy for ensuring Production matches UAT?
Any advice, documentation, or best practice would be appreciated. Thank you!
Regards,
Kishor
Ramkishor , In case of Microsoft Fabric, you should not create a view in SQL endpoint, it will lead to Direct Query not Direct Lake.
The way you should to isMake sure all columns, and Rename is done till the lakehouse level, whatever is possible
Create a Reporting Lakehouse in Reporting Workspace
Create shortcut from all other lakehouses to this
Create a semantic Model using this Lakehouse(Option in Lakehouse UI) and rename and measure creation in Semantic ModelRefer MS Fabric - Power BI Direct Lake Semantic Models
https://youtube.com/live/1HDxJASdSws
6 Replies
- amitchandak
Super User
Ramkishor , In case of Microsoft Fabric, you should not create a view in SQL endpoint, it will lead to Direct Query not Direct Lake.
The way you should to isMake sure all columns, and Rename is done till the lakehouse level, whatever is possible
Create a Reporting Lakehouse in Reporting Workspace
Create shortcut from all other lakehouses to this
Create a semantic Model using this Lakehouse(Option in Lakehouse UI) and rename and measure creation in Semantic ModelRefer MS Fabric - Power BI Direct Lake Semantic Models
https://youtube.com/live/1HDxJASdSws 
Murtaza_GhafoorHere is my recommendations
1-Keep all your SQL view scripts in source control so the same versions can be deployed across environments.
Deploy those view scripts to Production using automated CREATE/ALTER VIEW steps, not manual copy-paste.
2-Use Power BI deployment pipelines to promote datasets and reports and handle connection remapping.
3-After the Prod views are in place, simply update dataset connections (via pipelines, REST API) instead of rebuilding models.
RamkishorHi Murtaza_Ghafoor ,
Thanks for looking at this .
Could you please share me any references for the approaches you recommended? That will be very useful for me .
Regards
Kishor
- Murtaza_Ghafoor
There is no exact reference for this. Actually with my past employer i integrated ADO(Azure DevOps) with Fabric Workspaces for version controlling purpose & CI/CD Pipelines, thanks
v-prasareCommunity Support
Hi Ramkishor,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support- v-prasare
Hi Ramkishor,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support