Article Discussion: What's Best for DBAs? GUI or T-SQL Commands?

If you have any questions or comments about this article please post them here.

This forum post relates to this article

I agree with the author but i would like to add few more things to it.

Firstly, my philosophy is to use the enterprise manager whenever i can but look to osql if the circumstance isn't right.

You nkow, Enterprise Manager is a really really good tool. and I think people should use it when ever they can. Because, it allows you to see EXACTLY what you are doing. eg. you are not going to delete a table by mistake cuz it askes you do you want to delete these records..before they do em. (when you are trying to delete a row with specific id, you type DELETE FROM TableA WHERE ID=1 right? but u know things can go wrong when ur friends just come in and press F5 before u typed WHERE clause...NOT FUN) anyways...yeah..use enterprise manager whenever you can.

BUT sometimes, EM just isn't enough. eg...the example the author gave about the backups, renaming of database. then u really need to go to non GUI. I think this was the main reason author gave about his preference to CMD Interface rather than GUI.

BUT it is more likely that you might not even have access to EM or QUERY Analyzer most of the time ..then that's where it starts to test ur DBA abilities. (that's when u take out your usb drive containing your trusty osql ). And this happens alot often that the things author have mentioned which is when EM doesn't just have function to do things u want to. I mean how many times do u write a backup plan. or how many times do u rename a database?

So here is the bottom line...u use EM whenever u can but many DBAs will know that EM is a privilage and it is something that u can't alwaysa have access to..