It would really help with backwards compat and frustrations connecting in SSMS if Fabric SQLDB allowed users to connect to master.
This adds 2 improvements
1) In this way we could connect to SSMS and then change DB afterwards , which is very much a mainstream practice. we understand telemetry shows that this is the No1 connection error from SSMS.
2) Currently some features such as dacpac, VS package export from SSMS and 3rd party schema compares break due to this issue.
3 Comments
- fbcideas_migusrNew MemberStatus added:New
- akatesmith
Microsoft Employee
Status changed:NewtoUnder Review - akatesmith
Microsoft Employee
Status changed:Under ReviewtoAbandoned
Recent ideas
Restore "no-reply" option for Power BI Subscriptions
Please add a setting in the Power BI Subscription pane to choose the sender identity. With the recent update the platform forces emails to route through the subscription owner's personal Exchange On...LenaFid8 hours agoRegular VisitorNew300Views52likes11CommentsEnforcing OneLake Security on external semantic model API calls without adding security risks
Problem External applications cannot query Fabric semantic models on a user’s behalf - with OneLake RLS security rules enforced - unless the Fabric API is exposed to any and every client an authoriz...sean_cochran10 hours agoResolver INew21Views0likes0CommentsAllow ownership transfer (“Take over”) for Activator items
Activator rules run under the identity of the item’s creator. When that person leaves the organization and their account is disabled, all rules stop working silently. Unlike other Fabric items, there...ndelcastillo11 hours agoRegular VisitorNew29Views1like0Comments