SSMS crashes when try to modify database diagram (v18.2)

3

When I try to modify a database diagram created before the application restart and crashes when trying to access. It happen only when I save the diagram and close the application. When I try to reopen it throws me an error then restart the SSMS.

I'm running SQL Server 14.0.100 Express Edition.

I reviewed the Microsoft Event Viewer and I get this:

Faulting application name: Ssms.exe, version: 2019.150.18142.0, time stamp: 0x5d3573be Faulting module name: DataDesigners.dll, version: 2019.150.18142.0, time stamp: 0x5d3573f0 Exception code: 0xc0000005 Fault offset: 0x00004be8 Faulting process id: 0x5ec8 Faulting application start time: 0x01d56d761e232f6c Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe Faulting module path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Tools\VDT\DataDesigners.dll Report Id: e797c8be-6448-4547-9f6f-146cd92d8178 Faulting package full name: Faulting package-relative application ID:

sql-server
database
ssms
diagram
designer
asked on Stack Overflow Sep 17, 2019 by Ivan-San

1 Answer

8

MS acknowledged that there is a problem with Database Diagrams feature in the SSMS as of 18.2. You can use the previous SSMS version 17.9.1, which supports all features of SQL Server 2017 that you use.

In fact, they removed Database Diagrams feature in SSMS 18.0, then returned it back in 18.1 after people asked for it, but it has a problem.

In Release notes for SQL Server Management Studio (SSMS) under Known issues (18.2) there is an item:

Database Diagram created from on an SSMS running on machine A cannot be modified from machine B (it would crash SSMS). See UserVoice for more details.

Vote for a fix on UserVoice: SSMS 18.1 Crashes when Opening a Database Diagram

The MS Product Manager replied there:

I’d like to provide an update on this issue/

Unfortunately, it is proving to be pretty complex to deal with this this ancient technology that is used by SSMS. That’s why it’s being quite challenging for me to find a fix.

I’ll keep working on this, but sadly there is no fix in sight yet.

-Matteo

answered on Stack Overflow Sep 20, 2019 by Vladimir Baranov

User contributions licensed under CC BY-SA 3.0