Isaac
Lifelong Learner
- Local time
- Yesterday, 21:05
- Joined
- Mar 14, 2017
- Messages
- 11,401
Does anybody else agree that if/when you switched to SSMS version 18x, the experience was pretty messed up?
First, my settings were not preserved, although that could be something specific to my company and their install process - and thankfully, I was able to find the residual folder from 17 and import those settings!
Second, and this is the BIG one, double-clicking a .SQL file no longer opens in the existing/already-open instance of SSMS - it ALWAYS opens a new one. So instead of ending up with multiple document tabs in one instance, you end up with a gazillion instances.
Yes, I can drag a .sql file to the window and force it to open in an existing instance, but this is a huge loss from being able to just double click the file!
Third, if all I do is open a blank SSMS with no document/query, you know how the window title generally says Solution1? (even though you have NOT created a query/document window yet). Well, when I close the program under that exact scenario, it persists in asking me "do you want to save changes to solution1?", even though I haven't made any changes or edits and in fact, there isn't even a valid document window open!
I really hope they fix or adjust some of these things soon - it's driving me nuts. I'm sharing the pain because pain shared is pain halved, right?
First, my settings were not preserved, although that could be something specific to my company and their install process - and thankfully, I was able to find the residual folder from 17 and import those settings!
Second, and this is the BIG one, double-clicking a .SQL file no longer opens in the existing/already-open instance of SSMS - it ALWAYS opens a new one. So instead of ending up with multiple document tabs in one instance, you end up with a gazillion instances.
Yes, I can drag a .sql file to the window and force it to open in an existing instance, but this is a huge loss from being able to just double click the file!
Third, if all I do is open a blank SSMS with no document/query, you know how the window title generally says Solution1? (even though you have NOT created a query/document window yet). Well, when I close the program under that exact scenario, it persists in asking me "do you want to save changes to solution1?", even though I haven't made any changes or edits and in fact, there isn't even a valid document window open!
I really hope they fix or adjust some of these things soon - it's driving me nuts. I'm sharing the pain because pain shared is pain halved, right?
