Database diagrams on new release 18 not work
I installed SSMS 18.0 and cannot find Database diagrams folder. It is just missing. Where is the problem?
Ebrahim Karimi commented
WHERE IS DATABASE DIAGRAM?, PLEASE PUT IT ON ITS LOCATION
george pagotelis commented
You realize that not everybody is a C# code first guy????? Put the database diagrams back as we work database first!!
John Emil commented
put back the diagrams
Wayne Redelinghuys commented
Please put back the diagrams!
John S commented
I no longer have access to my diagrams. Please add this functionality back into SSMS.
With Office 365, if you let your paid subscription expire, Microsoft lets you continue to operate the applications in read-only mode to view the documents that you created while you were a paid subscriber.
With SQL Server 2000 through SQL Server 2017, I have created hundreds of diagrams in dozens of databases as part of my organization's database documentation policy. With Microsoft discontinuing diagram support with SQL Server 2019/SSMS 18, Microsoft is essentially throwing away all my documentation without my consent.
Please seriously consider implementing a documentation-only mode for database diagrams (as I have posted in "SSMS 2018 Database Diagrams - Display Only" https://feedback.azure.com/forums/908035-sql-server/suggestions/37442596-ssms-2018-database-diagrams-display-only).
I would like to have Database Diagrams again!!!!!!!!!!!
After Bill Gates left the company I've noticed too many bad things happening from products - MS Dynamics - out of the box not working on a freshly installed Windows Server systems despite several tries (and my sys admin friend telling me he was never able to install that for a client) to stupid things like breaking MS's own best practices by changing a Ctrl+Shift+S shortcut from Save As to Styles. What are the (presumably new) people in Microsoft thinking!?!?!?!
I've been a lead dev for over 15 years and I start all my app designs with a DB diagram (or a few) that help me figure out all the business logic I want to implement, keep expanding them as I build the app, use the feature to thread the joins like if I was designing a printed circuit board and even print them for quick reference.
My apps usually have between 70 and 150 tables and diagrams are an amazing way to have great overview of what joins to what, which are the keys, what fields are there in tables, or on a single tab of SSMS. I love them and they actually make my work enjoyable seeing the design grow and improve visually.
I really don't understand what's going on with you guys at MS.
Just recently I had big surprise where I found EF Core is sending multiple queries when I only write one LINQ expression. Big discussion. Apparently that behaviour by default is coming back in EF 3.0. But what are you people thinking!? I really do not understand. Please return back the diagram feature as well for the future. Huge vote from me for sure.
This is a massive change and there is no possible good reason to do it.
I guess if your database has less than 10 tables you don't need a tool like this, but that is not what SQL Server is for...
Shukhrat Nekbaev commented
Please return the diagrams! They allow me to quickly prototype, lookup and dev more conveniently. Moreover, ORM I use automatically picks up the changes in a couple of clicks. Schema sync to other dbs is done via another tool. I can't stress enough how visualisation is important for me.
MarkusS from Germany commented
Thanks to Microsoft making things worse and worse by removing proven functionality.
No new but less old functionality with v18?
*** Don't release new versions if you don't have the power to keep the functionality from the previous version - at least provide a suitable alternative! Visio is for sure not an alternative. ***
put back the diagrams
Please add diagrams back! we actually use them
Please consider adding your votes to the duplicate at at https://feedback.azure.com/forums/908035-sql-server/suggestions/35746747-database-diagram
MS has not properly used its own language with this. Deprecated means planning for removal in a future release. Diagrams and debugging have been *discontinued* (without the usual MS advance notice via deprecation).
Somebody in Microsoft has partnership with third parties that will offer this for a price! Improve it but not remove a tool without asking users or the deprecated feature will be the entire SSMS!
Deprecated to say deprecated, without reason!
A new low for MS. As a consultant for 15 years and a SQL team lead I use diagrams every day to to rapidly refactor schemas, prototype ideas, generate relationships, quickly add keys, generate data migration scripts (very hard any other way), generate schema change scripts for further productionisation, guide clients through the schema or entity relationships and most importantly teach new SQL devs the basics! It was an absolutely essential piece of my own path to loving and building Enterprise SQL systems. To remove it is beyond short sighted and actually worries me that the Product team really are completely out of touch with users.
For the SQL Product team to leave a single comment DEPRECATED in a release note is a total betrayal of the support we as MS software devs and proponents have given MS SQL over the years.
Please provide a blog post explaining the teams rationale and clearly lay out future plans or suggested migration routes.
Please can you also ensure 17.9 remains permanently available with Azure support as we rely on this.
I will be reaching out to as many of the "superstars" like Hanselman et al to see if I can bug them enough that this filters through to the team and we get the dignity of a response.
What could be a reasonable excuse to deprecate such an important tool?
Oh my.. are you actually kidding, this is an essential feature, our whole team rely on it? So MS just removed this huge capability without even a discussion with users? Is there any future plan to provide table visualisation? What was the thought process, do you even have a release note about it?