I really don't like the new SQL Server 2005 Management Studio.  I much
preferred the old SQL Server 2000 Enterprise Manager and Query Analyser.

The thing I hate most about Management Studio is this behavior: If I select
File/Open/File and then select a SQL script file to open, the next thing
that happens is that Management Studio displays a "Connect to Database
Engine" dialog box.  (This is just a minor annoyance.  In SQL Server 2000
Query Analyzer, opening a SQL script file didn't cause the "Connect" dialog
to show.)  But then after clicking the "Connect" button, the SQL script file
opens, but the active database (as shown in the "Available Databases"
combobox) changes from whatever database I was working in to the master
database.  The first time this happened I ended up running my SQL script and
creating a bunch of user tables in the master database instead of the
database I had been working in.

I find this behavior to be absolutely horrible!  Is there any way to change
this behavior so that the active database doesn't change when a SQL script
file is opened?  (I looked through all of the Options but didn't see any way
to change it.)

Thanks in advance,
--Rob Roberts

Rob,

Show quoteHide quoteYou can change the default database of the login you are using.

Dejan,

Thanks for that tip.  Yes, that helps, but I still much prefer the behavior
of the old SQL Server 2000 Query Analyser.  I work with multiple databases
on the same server, so I'll now need to remember to change the default
database for my login whenever I want to change the database I'm working
with.  But still, that's better than having the active database change to
"master" every time I open a new SQL script file.

Thanks again for the tip.

--Rob Roberts

Rob Roberts (robrRemoveT***@AndThisToo.pcisys.net) writes:
Try Edit->Insert->File, bound CTRL-Shift-P in the SQL 2000 keyboard.
It's not really as QA, but similar.

While I also prefer the QA behaviour, it's really funny seen in a more
general perspective. Which other editor would permit you flush a window
like that? But the key is that QA and Mgmt Studio are not really editors
for me. I only occassionally save any window from QA or Mgmt Studio.

And, yes, from a usabilty perspective I prefer QA a lot over Mgmt Studio.

Erland,

Thanks!  That's a little more like the Query Analyzer behavior that I
prefer.  I think I'll be using that all the time now, instead of File/Open.

I agee with that.  It's not that I want to use Management Studio to edit SQL
scripts.  I just want to sometimes use it to run SQL scripts that I've
created and edited with my normal programming IDE.

Thanks again!

--Rob Roberts

Am Fri, 18 Aug 2006 16:27:04 -0600 schrieb Rob Roberts:
....
QueryAnalizer from SQL2000 can be used for SQL2005 without problems. Only
debugging does not work :-(
And did you see EMS SQLManager? They have a free Lite-version too:
http://www.sqlmanager.net/en/products/mssql/manager

bye, Helmut

Helmut,

Unfortunately I did an in-place upgrade, and that seems to have uninstalled
the old SQL Server 2000 Enterprise Manager and Query Analyzer.  Can those be
reinstalled from a SQL Server 2000 CD without messing up the SQL Server 2005
installation?

I didn't know about that.  I'll check it out.

Thanks!

--Rob Roberts

Rob Roberts (robrRemoveT***@AndThisToo.pcisys.net) writes:
They should still be there in the 80\Tools\BINN directory.

But yes, you should be able to reinstall them.

Actually no, they aren't there.  There are still a bunch of DLLs in that
directory, but all of the EXEs are gone.

--Rob Roberts

Rob,

Don't know if you're still monitoring this thread, but just in case...

Anyway, I'm right with you on the differences between QA and Management
Studio.  The fact that it doesn't allow drag and drop onto an existing query
window to use the same connection is extremely annoying, as is the fact that
it defaults to master every time.

The only somewhat acceptable way around this that I've found is to create
script management projects in SSMS for each database you work with
frequently, associate all of the scripts with a connection in the project,
and set the default DB on that connection.  That way you can just
double-click the scripts and you'll get the right connection and DB.  It's a
pain in the ass to do initially, and it's still kind of restrictive because
you can't create sub-folders in the project to organize the queries, but it's
better than having to re-establish the connection Every. Single. Time.

I assume the reason for this new "feature" has something to do with
security, but this seems to be taking it a bit too far - it's as if you had
to go through a metal detector to get in your own car rather than just at the
airport.  Hopefully the next SP will at least allow an option to enable
QA-style behavior.

Mike,

Thanks for the tip on that.

I've gotten into the habit of doing as Erland suggested when I want to open
and run script file.  I use Alt-E-X to run the Edit/Insert File as Text menu
option, which then loads the script file into the current query window,
without re-establishing a connection and without changing to the master
database.  I still prefer the QA behavior, but the Alt-E-X thing makes SSMS
more tolerable for me.

--Rob Roberts

SIMPLE command to convert string to number? Not CAST or CONVERT.
Modifying Data Directly through Studio Manager
Table Truncated (Urgent)
SQL 2000 Database corrupt
Copy db to webhost server