Andy Bauman on 26 Sep 2024 01:09:49
Provide a way to add additional connection string parameters to a SQL server connection string within the following:
· Data Factory
- Data Flows Gen 2
- Data pipeline
- Data copy
- Power BI
- PowerQuery
- Paginated report builder
Ideally this would be managed from the Fabric connections UI. Something like "Advanced connection parameters" in SSMS (https://i0.wp.com/www.sqlerudition.com/wp-content/uploads/2015/02/ag_readonlyintent02.png?resize=426%2C501). This should enable extra connection parameters such as ApplicationIntent, MultiSubnetFailover, ApplicationID, WorkstationID, etc... Another example: (https://www.connectionstrings.com/ole-db-driver-for-sql-server/read-only-routing/)
These additional parameters should be able to be set at connection creation time, modified from the existing connections Fabric UI, and also be able to be set dynamically at run-time from the same applications/workloads listed above. I believe these additional parameters would also be useful for other SQL dialects.
We would like to pull our data from a read-only copy of our production DB. The ApplicationIntent=ReadOnly as is MultiSubnetFailover=True is critical for that, this can currently be set from DataFlows Gen 2 via a checkbox. Ideally all of the Fabric workloads would leverage a centrally managed repository for connection strings that would have this functionality. I believe we should have consistency amongst these connections and allow them to be used by every Fabric workload, including notebooks. My suggestion would be to also remove the checkbox from DataFlows Gen 2 in order to keep consistency between connections and not "bolt on" to connections in the Fabric connection repository.
- Comments (1)
RE: Add support for additional connection string parameters
When I submitted this idea, there was different spacing like this:Data FactoryData Flows Gen2Data pipelineData copyPower BIPowerQuery in PBI DesktopPaginated report builder