I'm sorry but Management Studio is slow, cumbersome and difficult to
quickly make changes while designing a new system.  It is directly and
very visibly impacting my teams production.  The same can be said for
developing databases though the Visual Studio IDE.

We are at our highest production when using Access ADP projects to
modify the database.  It's intuitive, familiar and very responsive.  Do
we have to wait until Office 12 before we have Access ADP / SQL 2005
integration?

Please PLEASE don't say this is not going to happen.  We are highly
dependent on this and have alot of infrasture in place based on this
setup.

C

I would like to expand on my dislike of Management Studio.  There is no
copy / paste for tables or views.  There is in Access.  There is no
Search / Replace in the SQL window.  You have to copy all to a text
editor to search and replace.

But I do really like the View Dependancies option though.

C

Hi
Well,  do you have SQL Server 2005 installled as  a named instance? I you do
, so a named instance is consumed memory which amy hurt a performance. Also
check out whether you have AutoClose of the database option checked.


In order to make 'copy /paste' as you like in Access you will have to learn
some  T-SQL commands as
SELECT * INTO NewTable FROM OldTable

In addition you have a great option in my opinon as Script Table As to make
changes and DML operations


Have you tried CTRL-F option in the Query Builder?





Show quoteHide quote

Uri,

Thanks for helping.  I'm trying hard to work with Management Studio.  I
know I can do anything with SQL commands, but I think the point of
having a tool like Management Studio is to make things visual and
easier.  It just doesn't seem very intuitive for rapid development.

CTRL-F is grayed out for me.  I can't seem to find the AutoClose option
plus I'm not for sure what it does.

I guess my frustration comes from the fact that I'm constantly being
forced to change my development process.  I'm spending more and more my
time and my development team's time learning new processes to do
basically the same thing.  VB6 to VB.NET, ASP to ASP.NET, FrontPage to
Visual Studio.NET, now Access ADP to Management Studio.  The products
we produce are basically the same, they just take longer to develop and
seem more difficult to maintain.  I think there is something to be said
about incrementally improving technologies instead of these huge
revolutionary leaps and then abandoning previous technologies.

Sorry for the rant,
C

Toughy Normalization Problem
Timeout expired - on a simple SqlDataReader:Read() call
Primary Key Question
Is it possible to join two tables in a View/Query where the Second Table is based on a Name in the F
OBJECTPROPERTY problem