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 :(
An error occurred while saving the commenttest commented
I found myself doing a total VS2019 SQL2019 with SSMS18.5 upgrade, thinking the SSMS issue with crashing that have been an issue for years now would be fixed.
I opened a new db diagram and all was working, I created a complex relationship schema..YAH it's working....
But as soon as I closed SSMS the crashing issue was there.
What are your developers actually doing, if I created software for a client the crashed all the time this would be my priority to fix it to keep my clients happy and we are not just clients we are developers working on your platform and promoting your products ?????
So from this I have found a work around...
Part A. Create your new diagram spend hours maybe days on it.
Part B. Never close your copy of SSMS again... Ever...Ever
Problem solved Microsoft, no need to thank me i'm here all week!
Work on this item has started. Will update as this progresses.
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
We’ll look at this for future release.
We are exploring how to implement this feature without compromising privacy. Thank you for all the feedback!
- Matt, Product Manager
We’re doing work to improve the alert quality, verbosity and API access in a way that will address most of the below.
Gilad Elyashar, head of product, Azure Security Center