I would like to set "not connected" tabs to a passive color like light gray to indicate they are not actively connected to a database. Current tab coloring is set by the connection, so this isn't possible. One possible implementation is to create an environment called "not connected" and then specifying NULL in the "SERVER" field.
This would be especially helpful for those who use SSMS's dark theme with SQL Prompt, because "not connected" tabs become nearly invisible with a black background and black font.5 votes
Ability to set a different TAB colour for read only connections to an instance e.g. to differentiate between connections to primary and read-only secondary in AOAG. This would need to inspect the ApplicationIntent=ReadOnly connection property. n.b. I have tried doing this with a registered server group containing just the one read only server, but it uses the TAB colour defined for that server, not the group, so cannot distinguish whether read-only or not.2 votes
The Tab Colouring system is brilliant, but I find that I am often working with more than one job at a time that are using the one Database. It would be of great benefit if I was able to Colour my Query Tabs based on which job they are for. i.e.: more than one colour available per Database.9 votes
Coloring the Tabs is very nice. I would love to have the database/server icons be colored (or at least a small colored dot on them) so I could see at a glance in Object Explorer what server the database is on.26 votes
- Don't see your idea?