Types of DBA's ???

  • "doesnt break anything" DBA 😀

  • vamsi056 (10/16/2012)


    Thanx.. Is there any production DBA, if possible can you/anyone give me a small description regarding all DBA types ..

    Accidental DBA: an application or user account that's been granted SYSADMIN membership by a Lazy DBA without cause.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Jr. DBA

    Chris Powell

    George: You're kidding.
    Elroy: Nope.
    George: Then lie to me and say you're kidding.

  • Female DBA (sure they exist and in response to your 'Gentlemen')

    Invisible/Non-existant DBA

  • Great Thank you so much, Now i want to delete this discussion but unable to due to funny replies 🙁

  • Well you can't delete the discussion anyway, so don't worry.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • This was removed by the editor as SPAM

  • To be honest, I don't believe that most people actually knew or currently know what a DBA actually does.  I think the job description of DBA started out with accurate roots but quickly warped into other things but the term "DBA" stuck as a convenient method to be found by job search engines, particularly in the last decade.  I know a lot of people (through interviews of them and myself) that think they know what a "DBA" is but don't actually have a clue because the term has become so nebulous.

    It is now being divided up into other "terms" like "System DBA" , "Application DBA", "Data Architect", "Data Scientist", etc, etc, yadda-yadda-yadda.

    The bad part is that the same thing is occurring to those "job position" titles as what happened to the term "DBA".  While there are real differences in the newer job descriptions, I'm finding that people are labeling themselves as those things when they're actually not and so those job descriptions are quickly being watered down, as well.  Yes, there are some (for example) real "Data Scientists" out there but a lot of unqualified people have labeled themselves as such on the resumes to "get the hits" and "get the job" or they just think they are one of those titles and they're actually just not qualified because they don't know what they don't know.

    It's like a lot of people who claim to be "Software Engineers" when very few actually are.  People just don't know what the term "Engineer" means, especially in the world of academia.  A great example would be that few people understand, for example, the difference between a very well qualified Chemist and a true Chemical Engineer.  The differences are not trivial.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Standby DBA

Viewing 9 posts - 16 through 23 (of 23 total)

You must be logged in to reply to this topic. Login to reply