Re: SQL Server Management Studio is one of the worst UIs I have de
- From: "David Gugick" <david.gugick-nospam@xxxxxxxxx>
- Date: Wed, 9 Nov 2005 10:57:20 -0500
Jim wrote:
> David,
> I disaggree its a perfectly good reason to put off a server
> migration. When a company reduces overall usefullness of existing
> tools I see no reason to upgrade. These are the applications I am in
> day in and day out why should I downgrade my productivity just to
> have the "latest and greatest" version of SQL server. The simple fact
> is these new tool are junk. Also why should I have to buy a 3 party
> tool just to get the same usefullness of the existing older product.
> I am usually the first to upgrade I love new tech but I will not
> tolerate downgraded slow interfaces for the sake of a pretty look.
>
I fear I may get off topic a bit, but I will say most customers will not
consider an upgrade to SQL Server 2005 (or an RDBMS) strictly on the basis
of the client tools. There's usually a business reason; i.e. a new feature
on the server itself that benefits the company as a whole that mandates the
migration. In those cases where migration is easy and provides little
back-end benefit, you're right, that the client tools could play into the
migration.
Having said that, Management Studio is a version 1.0 type product and will
probably be enhanced bit by bit with each new service pack/release. So, I
would suggest you do the following: Since I'm convinced Microsoft has every
intention of addressing its shortcomings, send separate emails to
sqlwish@xxxxxxxxxxxxx about current features you feel are not working as
expected or wish they worked differently. Also let MS know how to better the
product overall. I know that MS is already soliciting suggestions for the
next SQL Server release and I know that includes client tools.
You may also benefit from making specific posts in the "clients " ng to
solicit other opinions about certain features and how to improve things.
Making a transition to a completely new tool from one that has changed
little over the years is difficult. Most developers get very used to the
products they work with every day. Witness the transition from VB 6.0 to
VB.Net and the issues raised by those developers (and are still raised). No
one will disagree that VB.Net contains far more value to an enterprise, but
it does require a paradigm shift in the way things are done. To a lesser
extent, that's true with Management Studio.
So start some new threads about features you are having issues with and
let's have some real discussions about how to make the client tools more
productive for everyone.
--
David Gugick
Quest Software
.
- References:
- Re: SQL Server Management Studio is one of the worst UIs I have dealt
- From: David Gugick
- Re: SQL Server Management Studio is one of the worst UIs I have dealt
- Prev by Date: Re: bcp problem
- Next by Date: SQL 2005 (Express) - Can't connect with ActiveX SQLDMO
- Previous by thread: Re: SQL Server Management Studio is one of the worst UIs I have de
- Next by thread: SQL 2005 (Express) - Can't connect with ActiveX SQLDMO
- Index(es):
Relevant Pages
|
