@vindictive666 The challenge is that I'm not able to recreate this
locally. I am aware that it occurs for a variety of folks. But there is
something specific to environment or SSMS configuration that causes the
behavior.
@erinstellato When you say "opening new scripts" do you mean that you
have SSMS open already, and you double-click on an existing .sql file
through File Explorer and it opens another window of SSMS?That is
correct . It opens up a totally new SSMS instance .
@vindictive666 Can you please provide more detail about what you're
seeing, such as steps to recreate? When you say "opening new scripts" do
you mean that you have SSMS open already, and you double-click on an
existing .sql file through File Explorer and it opens another window of
SSMS?
Latest Comments