Sql-docs: Deprecated

[Brinsi]

I think the diagram is removed on your last version of SSMS

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a8bc803d-3aee-0e1f-ab64-31c5af48e9f9
• Version Independent ID: 472fcb4b-39c3-72a3-d2af-4eba68b72f04
• Content: Create a New Database Diagram (Visual Database Tools) - SQL Server
• Content Source: docs/ssms/visual-db-tools/create-a-new-database-diagram-visual-database-tools.md
• Product: sql
• Technology: ssms
• GitHub Login: @markingmyname
• Microsoft Alias: maghan

[VanMSFT]

Hi @Brinsi! Thank you for bringing this issue up to us! We really appreciate it. I'm assigning my colleague, Mark to investigate.

cc: @markingmyname

[TrevorMullen]

I'd just like to add my voice... removing one of the top 3 most valuable features from this product is probably going to hurt the product - quite a lot.
If the team can't make it work for Azure databases, we can live with it being grayed out for them, but for non-Azure databases, this feature is not optional.
Reverting to previous version now until you get this fixed.

[alesucman]

I Agree with @TrevorMullen. If this is a mistake you are forgiven. If this is intentionally hurting the product and removing a really nice feature I hope somone gets fired for a stupid decision like this. You will probably get a lot of hate messages so be ready. Not gonna look good on you resume.

[chadash]

it's really a stupid thing, why to remove productive thing?

[vincemic]

So I haven't used this feature in awhile. I just went looking for it for a brand new large project and I can't find it anywhere. Then I find this post. Seriously? Deprecated?

[markingmyname]

Thank you all for your suggestions and requests. We're on it. This will be discussed with the parties involved.

[markingmyname]

Hello to @Brinsi and to all of you,

There were some decisions made, but ultimately we are hoping to return the feature back in version 18.1 GA.

We apologize for any inconvenience.

Hope this helps.

Thank you.

[markingmyname]

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue.

[chadash]

Great, thanks.

[TrevorMullen]

Excellent news, thank you.

I't be really great if we could see a couple of updates to the tool...

I always use A3 size paper to get enough tables on the page.

I believe that an excellent addition would be an option to automatically add off-page-connectors as part of the page-break function. ie: any time your diagram takes more than one page to print, given the current scaling factor, this option will add a simple meaningful label (letter?) to each relationship line that crosses a page boundary.

Maybe even an option to colour code the tables??

eg: 1. automatically add colours based on the most heavily linked tables, working down to white only for tables with very the least links.

eg: 2. manually tag individual (important) tables to be colour coded. eg: tag people related tables as light-green and product related tables as light-yellow.

Note: it occurs to me that if your allow darker colours and the colours selected are too intense, the ability to select a different colour text may also be required. Or make the switch to white automatic when the intensity of the selected background goes over a limit.

[BenROhio]

@markingmyname, I hope this feature is indeed returned. It would be be nice if it was initially launched from a different location when it is brought back. Maybe adding diagram support to a database could be a right click option in the database and the Database Diagrams folder wouldn't appear until that was used.

It would also be nice if I could export the database diagram to a PDF with paper sized as large as is needed to make it fit if I had no intention of physically printing it.

Thanks.