hello this version should have database diagrams, this tool is very util
Closing as completed (please upgrade to SSMS 18.1+)
THANK YOU VERY MUCH!
For getting this working in 18.8!
We have many tables in our database and diagrams are important
Now If you would get the debugger working, life would be good
I face this "Index was outside bounds of an array" issue in SQL Server Management Studio V18.6.
Tokat, Erdinc (Istanbul) commented
I'm using version 18.1. The problem with DB Diagram is exactly that the diagrams created on previous versions can be opened, but the diagrams created on version 18 cannot be opened. please provide a solution to this problem.
Christian Velez commented
Running 18.2 and i'm having issues opening up my Database Diagram. Switched to "sa" for owner but it doesn't open up, just shuts the program down.
We also need that T-SQL Debugging tool gets back to the SSMS.
T-SQL is an embedded and procedural language and like every other PLs in the world should have a line by line code tracing and debugging facility for developers and in the home of development which is SSMS and not in any other IDEs like Visual Studio or third party IDEs/Tools. This is exactly a must both for dev and production environments. It becomes way more crucial when working with complex and heavily coded stored procedures. Please return it back soon enough like you did for Diagramming Tools. We fully appreciate it in advance you are listening to practitioners.
Thanks for brining back Diagrams
Thank you Microsoft for listening and responding.
Even if it did take everyone here and my tweet (https://twitter.com/WoestynKat/status/1137175081182851072) to get you to notice. You say removing database diagrams was not a mistake?
If not, then why would your user base be so impacted?
If still not, then why did you bring it back.
Up next: How do I debug triggers and stored procedures now that you've removed that too?
Dietmar Mueller commented
a small step for microsoft but a big step for the dba and the developer. or maybe the other way around?
it's good that microsoft has heard the voices of the community.
but would like to point out another remote essential feature: the tsql debugger. maybe not so popular, but still very valuable and important for many.
maybe the community can bring about a turnaround for microsoft.
thanks for voting and commenting
We rely heavily on the SSMS diagrams and will never upgrade from SQL Server 2017 or from SSMS 17.9.1 until we can bring our diagrams to the party.
We released SQL Server Management Studio 18.1 today. You can download it from https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017
We brought Database Diagrams back.
WTF. Put. It. Back. This is insanely stupid.
Anderson Luiz Ferrari commented
DB Diagram is an essential tool! Please bring it back
Keep yourself on v17 until they bring it back (otherwise we will have to move to another tool)
Instead of making it easier for devs, dbas and analysts, it seems that you're forcing us to do things the hard way or choose other systems. There's no point in that. Pls restore database diagrams.
Please bring diagrams back, creating relationships via code is slow and unnecessarily complex. I don't get why you guys would remove them instead of actually improving them. Or just leave them as they were.
This post, SSDT Diagrams, is a viable alternative.
Daniel Aubert D Amico commented
what the ****!!! Db diagram back please!
Mark R commented
Please bring back Database Diagrams in SSMS v18+. Maybe make the visibility in the tree configurable for those who insist on clicking it by accident. Thanks
Piotr Stulinski commented
Please bring this feature back.
Missing the database diagrams very much, always use it to prototype a database
Nick H commented
It is inexcusable this was removed. Did they even ASK any of their customers?