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
Fix Direct Lake semantic model binding in Deployment Pipelines
When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials....lk1234 hours agoAdvocate INew1.5KViews27likes2Comments:: operator for typecast in T-SQL
Introduce support for the ::type cast operator in Fabric Data Warehouse as syntactic sugar for the existing CAST(... AS type) expression. The new operator would be functionally equivalent and compile...jovanpop-msft6 hours agoMicrosoft EmployeeNew47Views7likes2CommentsAllow calls of Fabric SQL Database stored procedures from Data Warehouse
It would be great if there were a possibility to call a SQL Database stored procedures directly from a Data Warehouse stored procedures. A use case for this would be e.g. logging activities and even...Vojtech_Dolejsi8 hours agoNew MemberUnder Review2.9KViews13likes2CommentsPower BI - Org apps and cross-report drillthrough
This idea is a request to provide cross-report drill-through capability for org apps. This means being able to navigate between reports hosted in different org apps. The following sections detail why...TomMartens9 hours agoSuper UserNew1.3KViews24likes3CommentsSemantic Model 'Make Changes to this Model'
The link or action item to make changes to the importing Semantic Model is to obscure. Nobody looks down in bottom right corner of the Power BI Desktop window unless they want to resize the current ...RobRayborn10 hours agoHelper IVNew2Views0likes0Comments