Forum Discussion
Pipeline-switch DirectQuery model between different SQL endpoint servers
Hi mestee ,
Thank you for contacting the Fabric Community. If the SQL server (endpoint) changes in a DirectQuery model, Power BI recognizes it as a new data source. Deployment pipelines do not support creating and validating new data sources during deployment, which causes this error.
To resolve this, you can either use the same SQL endpoint across all environments or update and rebind the data source after deployment.
Helpful Reference: Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn
I hope this clarifies the situation. If I’ve misunderstood any part of your situation, please let us know.
Hello,
Thanks for the quick reply.
(1) We do not use the same SQL endpoint across all environments, so unfortunately, that isn't a resolution for us.
(2) I am not able to rebind the data source after deployment. The direct DirectQuery model uses previously established Service Principal connections (1 for each stage). After deploying the model from DEV to QA, in the QA model Cloud connections drop-down has options 'Default: Single Sign-On (Entra ID)' and the ~sql_dev connection that was previously established and is being carried over from DEV (and there is 'Create a connection').
That all said, I will mark your reply as Accept as Solution and if you have any other comments please feel free to reply for future readers.
As a side note, we were only trying DirectQuery since DirectLake isn't fully developed for our needs at this time. However, the performance I saw with DirectQuery (on a very small model/report) was such that it wasn't going to suit our needs anyways. So back to import we go for now....
V-yubandi-msftCommunity Support
Thanks for sharing. Please stay engaged with the community for future discussions.