Is GUI tool suitable for a DBA ?

    We have a very hot post on itpub.net talking about this, the poster is me. I think of this topic after receiving several times of AUL/MyDUL recovery requests for dropping tablespace or dropping tables by wrong mouse click on GUI utilities (OEM, Toad, PL/SQL Developer).

    Another reason was that after interviewing some people, I found lots of people cannot write the correct simple command, or did not know how to query performance data from some important "V$XXX" views.

    I prefer command line tools as a DBA. SQL*Plus, AnySQL, OTop/OPMon/OTune have been my favorite tools when managing and tuning a database. AnySQL have been my replacement of SQL*Plus for common queries, it's java based, do not need "COLUMN xxx FORMAT xxx" to adjust the column width. OTop/OPMon/OTune have completely replay the role of Oracle statspack for me.

    Of cause we should not blame the tools itself, in the first cases, they should do the privilege management better. For the second case, command line utilities may really help. What's your opinion?

Comments (1)

to use gui tools is not fault.

but you should try your best to know what did the gui tools done for you.

the same to same O/R mapping tools.

Post a comment

SCode:
Mail(*, but will not be displayed):
Home: