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
File level commit - Need the ability to edit the commit description
I tried the recently announce file level commit for Fabric items. One notable issue I have with the feature (testing this with a Fabric warehouse, I'm assuming this would hold true for other items): ...DataBard10 hours agoMost Valuable ProfessionalNew36Views0likes3CommentsAdd the known commit ID by the "updates" subtab
Often I have a git commit that I want to sync into a fabric workspace, today I never know if the browser tab has actually picked up the latest commit or if it is going to throw an error on conflicts-...T-Rez11 hours agoAdvocate INew9Views0likes1CommentFabric Deployment Pipeline Should Automatically Preserve or Upgrade Semantic Model Compatibility
Category: Microsoft Fabric — Deployment Pipelines | Semantic Models | Direct Lake The Problem When deploying a Direct Lake semantic model containing calculated columns or calculated tables throug...Murtaza_Ghafoor1 day agoSuper UserNew4Views0likes0Comments