Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Mark Duff

My feedback

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mark Duff commented  · 

    This same issue is spread among multiple comment threads, which dilutes our true fury over the arbitrary removal of SSMS diagrams (which should also have been in VS long ago). How many of we who have paid for it for years requested this? What exactly was the Use Case?

    Where is the sense of urgency in the midst of effectively destroying decades of architectural drawings caused by simply not including something that's always worked fine the the past?

    https://feedback.azure.com/forums/908035-sql-server/suggestions/37992649-ssms-18-1-crashes-when-opening-a-database-diagram

    Mark Duff supported this idea  · 
  2. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mark Duff commented  · 
    Mark Duff supported this idea  · 
  3. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Sorry folks, but we are not able to repro this issue (either using SSMS 17.9.1 or SSMS 18 Preview 7).

    Since multiple people out there are reporting this issue, it is obvious that we are missing something that is specific to your environment or configuration.

    Could you help us out and try to describe a little better your subscription/environment/account/permissions?

    For example, does the following mainstream scenario works for you all:
    1) Connect to Azure Portal
    2) Create SQL server+database
    3) Go to SSMS and connect to
    4) Add firewall rule

    If it does, then can you identify what is different between the case where it works and the case where it does not?

    Thanks,
    -Matteo

    Mark Duff supported this idea  · 
    An error occurred while saving the comment
    Mark Duff commented  · 

    As others have mentioned, I am master of my domain in Azure A. I am an elevated guest and AAD Directory Admin for the DB Server in Azure B. I receive this error when 1st login to the DB Server in Azure B while logged into everything, including SSMS as myself in Azure A.

    I could create an elevated User in Azure B used exclusively for SSMS connection. But doesn't that pretty much defeat the "S" in "SSO"?

  4. 1,884 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    204 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Unfortunately the complexity to implement dark mode into SSMS v18 is prohibitive and this item remains unplanned. Regular updates and improvements to SQL Server Management Studio are continuing, but most of the net new innovations in the graphical tooling space can be expected to be seen in Azure Data Studio.

    -Drew

    Mark Duff supported this idea  · 

Feedback and Knowledge Base