Re: Main difference: TOAD vs Enterprise Manager

I agree - learn to do stuff with SQL*Plus; I'm a contractor and move around a lot and find that some places will have OEM, some TOAD, some Quest etc. They all have SQL*Plus. I have a set of scripts which run in SQL*Plus to interrogate the database and these will ALWAYS work wherever I go.

TOAD (and other GUIs) can also be very dangerous - the place I am now uses TOAD, and since the Developers can connect into both Development and Production there is a risk they will be in the wrong place when they decide to drop that table.

However, sometimes it's better to use TOAD (you don't have to worry about "col tablespace_name form a15", "set pages 21", "set pause on" etc.) and it's also easier to browse objects.

As mentioned by someone else, TOAD is a Devlopment tool with a few useful features for DBAs. OEM is a full-blown Database Administrator tool. If you set it up correctly with all the agents installed (no mean feat) then it can do lots of stuff.

norwoodthree_at_my-deja.com (NorwoodThree) wrote in message news:<ba03e2c.0208121030.d1add64_at_posting.google.com>...
> The best way to go would be to learn to not use a GUI tool.
>
> However, if you wanna use GUI tools for DB administration, I've used
> DB Artisan (www.embarcadero.com) and it's pretty good. It's a Windows
> app unfortunately, but so is TOAD.
>
> I'd like to be able to tunnel some of these GUI apps thru ssh, but
> everybody writes Windows apps these days. Working via Windows GUIs
> thru VPN's suck.
>
> My .02.
Received on Mon Aug 12 2002 - 17:18:18 CDT