Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Apparently the source control in fabric is (still) not supporting SQL Analytics endpoint.
I have views setup in an analytics endpoint on top of a lakehouse, and use these views to load my data warehouse.
but these views are not stored in my source control and not supported during deploy too.
which means I have to rely on manual steps to deploy my stuff from my dev workspace to my prod.
is there any ETA to have a better source control support or deployment pipelines taking into account the dependencies? (pretty simple, deploy the tables in databases first (lakehouse, warehouse, sql database...), then deploy views and SP following the dependency tree)
and for now, what are my options if I want to automate my deployment process?
because I don't want to manage this manually anymore.
Hi @Jerome22 ,
I’m following up to confirm that all items discussed have been addressed. If there’s anything else you need, I’d be happy to assist.
Regards,
Akhil.
Hi @Jerome22 ,
Just following up to see if that clarified things around Lakehouse SQL views and deployment. Were you able to find a good workaround or log a support ticket with Microsoft? I know it’s not ideal having to manage views manually, so if you’ve come across any helpful scripts or automation ideas, feel free to share always happy to collaborate on smoother solutions.
Regards,
Akhil.
Hi @Jerome22
Thanks for bringing this up. As of now, SQL views created in the SQL Analytics endpoint of a Lakehouse aren't automatically tracked in source control (like Git) and aren't supported in deployment pipelines. That means views and stored procedures need to be manually recreated or scripted, and dependencies (like tables before views) don’t get handled automatically.
If this limitation is affecting your workflow, I’d recommend raising a support ticket with Microsoft so it’s officially logged and can help influence future improvements. You can do that here.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Akhil.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
29 | |
15 | |
6 | |
6 | |
3 |
User | Count |
---|---|
50 | |
44 | |
15 | |
7 | |
6 |