How to change sql database destination in DF2 in deployment pipeline?

[abpgupta]

Hi All,

I have created a DF Gen 2 to load data to Fabric sql database and I am able to deploy to next stage via deployment pipeline. However, In Dataflow destination still shows mapped to Development stage database. Is there any way to change destination to respective stage database?

Thanks for inputs.

[v-pgoloju]

Hi @abpgupta,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @Nasif_Azam  for prompt and helpful response.

Just following up to see if the response provided by community member were helpful in addressing the issue.

If one of the responses helped resolve your query, please consider marking it as the Accepted Solution. Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[abpgupta]

Could you please respond to follow up clarification? This is a bottleneck for SAAS to not able to use UI components without changing code for each stages.

[Nasif_Azam]

Hey @abpgupta ,

In DF Gen2, the SQL Database destination mapping does not automatically change when you promote through a Deployment Pipeline, it stays linked to whatever connection you configured in Development. To point it to the respective stage database, you need to:

1. Create separate connections for each stage (Dev, Test, Prod) pointing to the correct Fabric SQL Database.

2. In your Deployment Pipeline settings, go to the Dataflow’s dataset parameter or connection mapping for the stage.

3. Edit the connection mapping so that the dataflow in Test points to the Test DB connection, and in Prod points to the Prod DB connection.

4. Publish again or trigger a refresh, now the dataflow will write to the correct database in that stage.

Currently, there’s no “auto-swap” for DF Gen2 destinations like with datasets. You have to set the mapping manually in each stage after deployment.

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam

[abpgupta]

Thanks for response.  Is there any plan to implement it in future to make it easy to manage connection without causing differences in deployment pipelines?