SSMS 18.1 Crashes when Opening a Database Diagram
SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.
I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.
You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.
Latest bits for SSMS and SQL Server 2017 installed today.
SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.18362
The fix for database diagrams was included in SSMS 18.6. For more information, please see https://cloudblogs.microsoft.com/sqlserver/2020/07/22/sql-server-management-studio-18-6-is-now-generally-available/.
JP Doffing commented
Fingers crossed... I'll believe it when I see it though...
Toby Riley commented
Tony Donley commented
FINALLY!!! Thank you, Thank you, Thank you!
Dwaine W. commented
Great news, thank you!
Alex Chianuri commented
Exciting! Looking forward to it. Diagramming tool is one of the best features of SSMS; appreciate your effort to keep it alive.
Over the years my company has relied on the diagrams to help document databases and convey knowledge between groups. I and my co workers appreciate your efforts in fixing the problems in the diagramming tool.
I have this problem too. SSMS 18.5.0
Oscar Saenz commented
Well what a surprise, now it been for a while that I use MS SQL server and I do believe it is a powerful DB engine, and SSMS is it by all means the perfect tool to do support on SQL DBs. But now looks like MS is hijacking their own products, I had to use the BKM to go back to an older version 17.9.x in order to get the Diagrams feature to work back, cause by mistake I did the upgrade to the 18.5.
Not sure is someone from the development team is taking care of collecting from the clients and users, bug and errors so they can be put on a dashboard and address them by criticality.
This problem is not new I check and just in this forum they placed the 1st complain back in October 2018, YES 2018. This is just unacceptable from a company that has the reputation earned by year of developing great tools and products.
You are forcing the community to start seeing other solutions, cause developers are not trusting MS Dev team any more.
I would accept that you had issues with a new product, but MS SQL is being widely use.
Another thing who in the world will place a post as replay saying "I regret to inform that I did not get to fix this for SSMS 18.5" Where is Quality and Control on these team. where they force to publish this, this is a joke and a very bad one.
Perhaps are other interest to sell the code to a third party and force people to buy the Diagram designer tool.
Muhammed Şeker commented
We are so sad really, when be fixed?
Dave Wils commented
Didn't make 18.5.1 either...
Marcus Koch commented
your comment is almost 3 months old. When will it be fixed?
Wow. I wish I had your job security. I'm sorry I couldn't do it but I don't care ... clearly you have no idea or interest in how real sql dbas work. Otherwise, you would care.
when is fix planned?
Ahmet Bircan commented
when I want to modify database diagram ssms is crash and restarting ssms. I can't open and modify old diagram.
Matteo Said ;
I regret to inform that I did not get to fix this for SSMS 18.5, you may have read in the Release Notes.
I’ll be on this as soon as I can. I feel bad… I know :(
is there any improvement on this subject?
Miguel Arroyo Pérez commented
Every self-respecting SQL editor has a diagram editor. Since the update of 18.0 I have been constantly consulting this page, and I only see a lack of empathy. How do you explain to a client that the diagram could not be had in time, because I occurred to you to update Management Studio?
Now, there is no new feature in Azure SQL or any other functionality that justifies the delay in bringing the diagram editor back to our Management Studio.
The development team should lock up for a weekend, and get this over with. The current diagram editor of 18.5.1 does not work correctly either. As a counterpart, we could accept a renewal of the diagram editor, so that the format can be changed to the classic IDEF1X diagram style (which is what people who pay us understand), and others that may appear in the future.
It's crazy having to install Visio 2010 (it's still available on the previously called MSDN, now Visual Studio) in a brand new Window 10 version 2004 to make diagrams that are essential to present to customers.
Many times I think that there is some kind of conspiracy against SQL Server developers, by application developers, who are the ones who update our Management Studio. Maybe it is to check how many developers and clients really depend on traditional development, which is the only one that really works and with which you can guarantee the high production software (even if it is for use in AZURE)
I have been using Microsoft tools for more than 20 years, and sometimes decisions are made that work against their own technology and developer community.
Give us back the diagram editor or we leave the cloud !!
(It is a rhetorical claim, of course :-)
Fran Tonković commented · June 25, 2020
Matteo, we hope you are alive and well. Take your time and don't let dissatisfied _PAYING CUSTOMERS_ stand in your way of happiness.
Fixed it for you.
Daniel Seara commented
Guys, deprecating Database Diagram make not sense at all. Shall we start a change org signature colection to show you how much people use it?. If you are not capable to fight with an "ancient teclhnology" as Matteo says, look for someone having the ability. Consider roll back your deprecation :). Best regards.
Fran Tonković commented
Matteo, we hope you are alive and well. Take your time and don't let dissatisfied users stand in your way of happiness.