List of issues in Management Studio

I have been using Management Studio for a few days and it's full of
annoyannces.
1- I just tried to copy 200 rows from a table from Management Studio to
another similar table with a column that doesn't allow nulls. So I get the
same error popup message for each row and I can't cancel from this batch.
2- Why can't I multiselect tables and Stored procs to delete like I used to
in 2000's Enterprise Manager.
3- When I script a stored procedure in 2000's Enterprise Manager, I woule
the create, drop and permission statements ALL in one script. This way I
was able to recreate the SP in one shot even if it exited. Not in
Management Studio. The drop and create are two seperate functions. If you
wanted to script the grant permission, you have to do it from the database
level and go through a bunch of clicks just to do it for one SP. TIME
CONSUMIUNG!
4- So I decided to script the grant permissions from the database level
using the drop procedure and tell it to include the object-level
permissions. The generated script included the drop statements but no
grant statement. I guess it figured that if you're dropping the SP's, why
include include the grant statements' My idea was that the drop statements
are in one line so then I can delete them pretty easy. It didn't work.
5- As mentioned in my previous message, the import export wizard stops too
often and gives cryptic messages without indicating why it stopped in clear
English. That's why I resorted to copy and paste ( see 1)
6- I don't think the import/export wizard is smart enough to transfer the
child tables first to avoid the foreign key issues. This was a problem in
2000
7- When the transferring many tables which have identity columns, I had to
check the "Enable identity insert' checkbox and select 'delete rows in
destination table'. Is there a way to select this option for all tables
instead of doing it one table at a time?
8- Choosing 'modify' for a table and opening a table give the same exact
icon and text in the list of opened windows. There's no visual clue when
trying to select either.
9- No 'back' button in the last step of the import export wizard if the
wizard ran successfuly. This means if I want to select other tables, I have
to restart the wizard. See 10 below for why it's annoying.
10- The wizard doesn't remember my settings. I constantly transfer data
between two sql servers, the first uses windows authentication (local
server) and the other uses sql server authentication and the wizard always
defaults to windows authenitcation for both. I wish there's an option to
remember type of authentication, my username and password or at least
remember the type of authentication and username.
I hope these issues will be addressed in the next version.
John DalbergIf you want to make MS aware of issues with their products, use the Product
Feedback web-site at
http://lab.msdn.microsoft.com/productfeedback/.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Dalberg" <nospam@.nospam.sss> wrote in message news:20060329013741.245$vZ@.newsreader.co
m...
>I have been using Management Studio for a few days and it's full of
> annoyannces.
> 1- I just tried to copy 200 rows from a table from Management Studio to
> another similar table with a column that doesn't allow nulls. So I get the
> same error popup message for each row and I can't cancel from this batch.
> 2- Why can't I multiselect tables and Stored procs to delete like I used t
o
> in 2000's Enterprise Manager.
> 3- When I script a stored procedure in 2000's Enterprise Manager, I woule
> the create, drop and permission statements ALL in one script. This way I
> was able to recreate the SP in one shot even if it exited. Not in
> Management Studio. The drop and create are two seperate functions. If you
> wanted to script the grant permission, you have to do it from the database
> level and go through a bunch of clicks just to do it for one SP. TIME
> CONSUMIUNG!
> 4- So I decided to script the grant permissions from the database level
> using the drop procedure and tell it to include the object-level
> permissions. The generated script included the drop statements but no
> grant statement. I guess it figured that if you're dropping the SP's, why
> include include the grant statements' My idea was that the drop statement
s
> are in one line so then I can delete them pretty easy. It didn't work.
> 5- As mentioned in my previous message, the import export wizard stops too
> often and gives cryptic messages without indicating why it stopped in clea
r
> English. That's why I resorted to copy and paste ( see 1)
> 6- I don't think the import/export wizard is smart enough to transfer the
> child tables first to avoid the foreign key issues. This was a problem in
> 2000
> 7- When the transferring many tables which have identity columns, I had to
> check the "Enable identity insert' checkbox and select 'delete rows in
> destination table'. Is there a way to select this option for all tables
> instead of doing it one table at a time?
> 8- Choosing 'modify' for a table and opening a table give the same exact
> icon and text in the list of opened windows. There's no visual clue when
> trying to select either.
> 9- No 'back' button in the last step of the import export wizard if the
> wizard ran successfuly. This means if I want to select other tables, I hav
e
> to restart the wizard. See 10 below for why it's annoying.
> 10- The wizard doesn't remember my settings. I constantly transfer data
> between two sql servers, the first uses windows authentication (local
> server) and the other uses sql server authentication and the wizard always
> defaults to windows authenitcation for both. I wish there's an option to
> remember type of authentication, my username and password or at least
> remember the type of authentication and username.
> I hope these issues will be addressed in the next version.
> John Dalberg