Do you think SSMS is slow?

Well there are a few reasons for some slowness.

One of them is when you display the details of a job. SSMS executes sp_helpjob which returns ALL jobs, even though your only displaying ONE.

If you think this sucks then vote now to try and get this fixed.

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=140010

Free SQL Server Management Studio from bad code

-
Published 18 September 2006 23:35 by simonsabin
Filed under: , ,

Comments

19 September 2006 13:20 by help.net

# Do you think SSMS is slow?

Yes totally agree with Simon about SQL 2005 Server Management Studio, it sucks! Too slow, too slow. I
20 September 2006 06:04 by John Walker

# re: Do you think SSMS is slow?

I agree it's slow. I think they tried to do too much with one tool. It's now Query Analyzer, Enterprise Manager, as well as other stuff.

Also, I've run into some issues with the new replacement for DTS. I had to flow a database from SQL Server to Oracle, and it keeps bombing out on me. I took the same database under Enterprise Manager and it flowed into Oracle beautifully. Not good.
20 September 2006 21:19 by simonsabin

# re: Do you think SSMS is slow?

I have to make the point that I don't think SSMS sucks. What sucks is MS not removing some very bad code that makes a one feature slow.

I think SSMS is great, admitedly I hated it to start with, but once you get used to it it rocks.
Best features
Cancel Connection
Change Connection
Asynchronous tree view

21 September 2006 09:03 by John Walker

# re: Do you think SSMS is slow?

Simon,

I don't think I said SSMS sucks, but there are some issues I'm running into.

For example, tonight I tried to import an Excel spreadsheet into a table I have. Whereas in the past, DTS brought it right in with just the data, tonight it brought in the data, with an addition 4000 rows of empty data from the spreadsheet.

Sure, I simply did a DELETE FROM <TABLE> WHERE ID > XXXX, but I re-ran the same job through DTS and DTS did the right thing.

I'm surely going to be working with this tool for the next 3-5 years, so I think it's important to point out the problem areas.