Discussion on SQL Server Mgmt Studio 2005

antic

Perch
I'd like to use this thread to encourage people to install and start using the new SQL Server Management Studio 2005, because I have and is seems to be a LOT faster than EM.

One thing I've noticed is it doesn't respect the server-side settings Jodo made to list only owned databases, but it doesn't matter - it gets and lists the 500+ databases on a server in a few seconds instead of waiting over a minute!

Saving changes to a table structure seems quicker also, which has always been a big time waster in EM; also just takes a few seconds, though I haven't tried changing something which affects a range of other tables at the same time, which is where EM really slows to a standstill.

The interface is more like Visual Studio than EM, so be prepared. :) It does have some advantages. But I'd like to see what everyone else thinks of it, definitely worth checking out.

The Management Studio 2005 download page is here.

The prerequisites are:
1. MSXML6
2. DotNet Framework 2.0
 
I bought MS SQL Server2000 Developer Edition. And I am still using the jodo-supplied EM because I can't figure out how to connect to a MSSQL server at jodohost using the MS tool.
If anyone out there can point me in the right direction, it would be much appreciated.

And more particularly to this thread: Is this a similar tool to what you are using? Do you know of a compelling reason for me to NOT persue using the MS tool I bought?

Thanks!
 
Briefly (coz it's 2:3am here:)) do the following:
1. open the Client Network Utility that would have installed with your Microsoft EM.
2. Go to the Alias tab
3. Click (on the left) on TCP/IP
4. Enter a name for your database at the top (eg. "client xyz database")
5. Enter the IP address of the sql server database (see your CP for that). Leave "dynamically determine port" ticked.
6. Click OK.
7. Open EM
8. Right-click on a server GROUP node, and select "new SQL Server registration" (or first create a group if there isn't one).
9. In the properties dialog, dropdown the list of servers and select the one you created in the Client Utility.
10. Click the option "sql server authentication" and enter your db's login and password for your db user account (again see the CP for that).
11. Click OK. It should register the database.
You should now be able to browser your database.

hth
 
antic said:
...I'd like to see what everyone else thinks of it, definitely worth checking out...[/url]

Hmmm... No SQL Server agent means no scheduled DTS packages run on my local machine. Guess I'll just wait...
 
Back
Top