MicrosoftHi jehayes, in the extension to @Bob_Duffy's question
I’d like to discuss a deployment issue we're encountering and get your insights or possible solutions.
We’ve set up our pipeline using the medallion architecture, following your guidance to use Azure SQLDB for auditing and metadata management. However, during deployment, we’ve run into a challenge. Our setup includes four workspaces (dev, QA, UAT, and Prod), each with its own dedicated Azure SQL database for metadata.
The issue is that we currently lack a way to dynamically configure the Lookup connection to automatically point to the appropriate Azure SQL server for each environment. This limitation forces us to make manual changes within the data pipeline activities wherever the Azure SQL connection is used, which is inefficient and prone to errors.
Do you know of any workaround or solution that could help us avoid this manual intervention and dynamically handle the Azure SQL connections?
Thanks in advance for any guidance!
