Tasks on First day as a Fresh DBA
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Tasks on First day as a Fresh DBA

  1. #1
    Join Date
    Sep 2006
    Posts
    2

    Tasks on First day as a Fresh DBA

    Hi Can some one please briefly tell me what steps (each steps) a DBA should take on a new job to perform as a general database administrator?

  2. #2
    Join Date
    Sep 2006
    Posts
    2
    Friends, I have my first day on job in the morning. Need help pleaseeeeeeeee..................

  3. #3
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    First, you need a little patience. Next, you need to plan a little better and ask these questions so somebody has enough time to give you a decent answer.

    I'm sure the people that interviewed you know about what your skills are. You most likely will spend the first day filling out forms and reading. Be honest with your supervisors and I'm sure they'll challenge you.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  4. #4
    Join Date
    Feb 2003
    Posts
    63
    Is this a new job as a DBA ? Suely you knew enough to get through the interview.

  5. #5
    Join Date
    Mar 2004
    Location
    DC,USA
    Posts
    650
    Boring!!!

    The day moves very slow.
    "What is past is PROLOGUE"

  6. #6
    Join Date
    Jan 2001
    Posts
    3,131
    You should randomly assault one developer with a rusty pipe wrench for no apparent reason, when asked why just say he/she had bad timing.

    This will make them all fear and respect you in the future and your job from here on out will be much more enjoyable.

    Set the tone NOW!!
    He who hesitates is lost.
    I remember when this place was cool.

  7. #7
    Find out what the backup strategy is and verify that the backups are working. Restore them to a seperate system to make REALLY sure.

    Find out how you'll know if the DB backup scripts die.

    Find out what is monitoring the database -- how will you know if it fails? What if the server itself fails -- who gets called?

    Make sure the layout of the DB isn't suicidal -- such as backups being stored on the same disk (NAS) or machine as the database.

    Do a security audit and find out what all the accounts do if it is not obvious. The exercise of tracking this information down will help integrate you into the environment and perhaps find some accounts that don't need to be there.

    Check on the growth rate of the database -- make sure it isn't going to run out of disk space in the next few weeks, otherwise start getting more disk space immediately.

    You never know what your predecessor has left for you, so taking care of these will at least give you some confidence that the system isn't going to fall over on you your first day.
    Last edited by jhmartin; 09-22-2006 at 01:44 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width