Re: Remote DBA

I also like Matt's glass half full definition of "ticket closer". The
ability to prioritize and work tickets is an important (and not easy) skill.
 However, I've been using that same nickname for years, but in a
more derogatory way.  There are some DBAs (but this mentality affects
developers too) who will take the path of least resistance just to be able
to close a ticket. And close many of them.  For example:

Ticket:  Investigate ORA-01653 in UAT

Action: alter database datafile
'/u01/app/oracle/oradata/important_tablespace01.dbf' resize 1000m;

Ticket State: closed

But then, only  to have this same issue rear is ugly head in PROD the next
day.  I think a more important skill is to effectively work a low priority
ticket to completion so it never becomes a critical one.  I also like
verbose descriptions of the resolution path and copy/pastes of the exact
commands so they can be easily understood and reproducible.

I get very worried when I see a resolution that only consists of "Done".

Other related posts: