That colors the connection status bar for the editor, but it doesn't color the tab.

Wait "tab border colors"? Where are you setting that?

Without knowing more information, it's difficult to understand what else is at play. It takes 7 seconds on my machine, SSMS 21 takes 10 (not including connection dialog).

We can, and do, prioritize more than one thing at a time. feedback.azure.com/d365communit... 🤷‍♀️

I'm honestly not sure what to tell you. Installing the tool is an extra step, it's not available by default, and it doesn't automatically apply hints. Applying hints using Query Store Hints is low risk and easy to un-do.

Yup. Thanks Alex.

Also, I'd argue that we are not "pushing" bad practices. We're providing a tool to help folks identify what hints may improve query performance.

What do you mean "like the index recommendations"? There's a time and a place for query hints - there are a lot of scenarios cannot change code directly (third party app) or immediately. Query Store Hints are a great solution in those scenarios, but how do you know which hint is "best"?

Windows ARM64.

What is "awhile"?

Hi - what version of SSMS are you using? We've made a quite a few improvements lately, not related to Copilot. I'd hate for you to be under the impression that's the only thing we've prioritized.

We have a feedback item for this, and we don't have a fix yet, but it's something we are looking to address.

It's optional, you don't have to install the Copilot component if you don't want to use it. What are your other reasons for staying on an old version?

SSMS never automatically re-opened tabs after closing. The only scenario that occurs is when it crashes and it tries to recover them for you.

Are you looking for SQL 2025 support?

Those are the only ones supported.

Needless to say, I’m in the exit row.