Home Dashboard Directory Help
Search

Microsoft SQL Server Management Studio by david_tolkien


Status: 

Closed
 as Won't Fix Help for as Won't Fix


3
1
Sign in
to vote
Type: Suggestion
ID: 228719
Opened: 10/17/2006 3:56:53 PM
Access Restriction: Public
0
Workaround(s)
view

Description

I must apologize in advance for the harsh comments to follow.

When I first heard about SQL 2005 I was excited. All of the reviews and features to be added in got me excited to try it out.

About a month ago I finally had the opportunity to use the product. I cannot describe to you how disappointed I am. The new SQL engine might be awesome, it may not. All of the new features that you included might be the greatest thing in the world but I couldn't tell you. The GUI is so bad that I do not want to use the product.

I have to ask if anyone at Microsoft actually uses the Management Studio? If not please let me know what tool you use so that I can use it also. I find it extremely difficult to believe that you use it. I feel that the GUI is designed to be used by a high schooler, not a professional.

I cannot believe that anyone in your organization used this GUI. The most basic tasks take 10 clicks. Even then you cannot get the results that you want. I cannot figure out how to script the database and have it return a result that includes both drop and create statements.

I always considered Enterprise manager to be a bit slow but it kills Management Studio in performance. To be honest I feel that Management studio was designed by a comity of managers without any input from a developer. It looks very pretty and has all of the right "features" but is completely useless.

I tried to use the Management studio but it is so slow and clunky that I had our IT install Query analyzer. I tried to get back Enterprise manager but was informed that SQL 2005 removed it from my system and they cannot restore it. What more it cannot interface to SQL 2005.

I had always thought that Oracle designed the worst software tools. You have hands down beaten them.

I love SQL 2000. The tools that came with it made my job so much more productive. There were quirks and oddities when we switched from SQL 7 to SQL 2000. Some of us preferred SQL 7 over 2000 but I don't know of anyone that said they didn't want to switch or couldn't get their job done with the new tools.

With Management studio I have yet to find anyone that likes it. There are feature that are provided in SQL 2005 that we like but I don't know of anyone that likes the tool. Even within those features that we like how they are presented by Management Studio makes our life difficult and makes us want to use them less. Everyone wants Query Analyzer to be installed on their system because it is a better tool.

If management wasn’t forcing us to migrate to SQL 2005 we would recommend not migrating simply based on the tools provided. This is in spite of the new features that we want to use.

David Besselievre
David.Besselievre@oati.net

Details
Sign in to post a comment.
Posted by Microsoft on 10/19/2006 at 1:47 PM
First off, I apologize you've had such a negative experience with the new toolset that is provided with SQL Server. We have completely re-written the infrastructure for our tools to lay the foundation for the future. Unfortunately, there were quite a few areas where we could not reach parity with SQL Server 2000. We have been working very hard to address the concerns of our SQL Server 2000 advocates. Much of the effort can be seen in Service Pack 2. Please take a look at the tools improvements we've done in Service Pack 2 when it is released, and let us know what is still missing.

As for the specific suggested you mentioned...
"I cannot believe that anyone in your organization used this GUI. The most basic tasks take 10 clicks. Even then you cannot get the results that you want. I cannot figure out how to script the database and have it return a result that includes both drop and create statements."
This feature was in SQL Server 2000 and was missing in Management Studio. It has been added back in Service Pack 2. Just go to "Tools | Options... | Scripting" and change the default scripting settings.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
Sign in to post a workaround.