IN SQL Server 2000, we didn’t have the fancy-schmancy Management Studio…we had Enterprise Manager and Query Analyzer, and we liked em, by gum. You know, give or take.
I am very fond of SSMS, but there’s one small thing I miss about QA and the olden days: You could open a query window without connecting to a database. I liked that, I miss that. Why, O mighty Microsoft, make that a requirement? If I’m developing something and want to look at an old version, or compare to a different query, why force me to make a connection for each and every little query window? Meh.
Edit: Several of you have spoken up, so I edit my complaint: I wish it were as convenient as it was in 2000 to open a disconnected query window, and to disconnect an open query window. Here are the suggestions, and my results:
- Use File > Open > File Disconnected. – Okay, that works. I hate not having shortcuts and hotkeys, though.
- Just cancel out of the connection dialogue. – This won’t disconnect an already connected window. And, it doesn’t provide me with a disconnected new window, unless…
- Use the “Database Engine Query” button next to the “New Query” button, and cancel out of the connection. – This works. Still irritating, though. What’s wrong with CTRL-N, Cancel?
Thanks for the input Mladen, Adam, and Tim! I’m glad to find out it’s possible. I’m still keeping this as a small wish, though…
Happy days anyway,
Jen McCown
http://www.MidnightDBA.com/Jen
Actually, there IS a way around. At least in SQL Server 2005, instead of using the New Query button, use the Database Engine Query button immediately to the right of it. Click ‘Cancel’ when asked to connect, and you’ll still have your unconnected query window open.
That works in 08 too, plus there’s a…well, I’ll edit the blog post. Thanks, Tim.
“File… Open… File Disconnected” works as well.
Oops. You already kney that. Sorry I didn’t see that in your post. 🙂