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.
3 Comments
- fbcideas_migusrNew Member
When I submitted this idea, there was different spacing like this:
Data Factory
- Data Flows Gen2
- Data pipeline
- Data copy
Power BI
- PowerQuery in PBI Desktop
- Paginated report builder
- fbcideas_migusrNew MemberStatus added:New
- g170479New MemberAny updates on this?, We are getting hit on this one, just wondering if there is an item on the horizon for this.
Recent ideas
Allow External OneLake Data Shares to Be Accepted into Multiple Fabric Item Types
Fabric External Data Sharing provides an excellent zero-copy mechanism for sharing OneLake data across tenants. However, the receiving tenant currently has to accept the share into a Lakehouse. I w...Mourak6 hours agoNew MemberNew5Views0likes0CommentsAllow OneLake Shortcut Authentication Mode to Be Changed In Place
OneLake shortcuts support passthrough and delegated authentication, but changing the authentication model currently requires deleting and recreating the shortcut. I would like shortcut authenticatio...Mourak6 hours agoNew MemberNew6Views0likes0CommentsTenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently av...Mourak6 hours agoNew MemberNew6Views0likes1CommentAdd an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented s...Mourak6 hours agoNew MemberNew3Views0likes0CommentsImprove CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinat...Mourak6 hours agoNew MemberNew2Views0likes0Comments