Prduction DBA

  • Dear Friends ,

    I am moving to work on Production support as DBA ,plz any tell me any body what are the common responsibilities of DBA to work on Prod support ,

    Thanks from

    E.Pavan Kumar

  • You have to ensure your databases are available, reliable, and recoverable and their performance meets SLA.

    Always remember this: DBA owns the structure but never ever the data.

    _____________________________________
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at Amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
  • Always have the backup handy..make sure there is no corruption of data...thanks!!

    The_SQL_DBA
    MCTS

    "Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

  • Last but not the least would be troubleshooting issues as and when they come..well to be a good DBA, investigate the problem before the users call you..hey somethings wrong with the DB..somethings slow...work to avoid this situation or may be get used to these questions..thanks!!

    The_SQL_DBA
    MCTS

    "Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

  • Thanks for your kind reply ,

    regards..

    E.Pavan Kumar

  • There are different types of production DBA's. Some manage databases that are internally developed, and they need to know the structures, code and have a good knowledge of performance tuning Physical Structures and Code. Some manage SQL Servers that have databases provided as part of applications, and they also need to have a good knowledge of troubleshooting performance problems to identify which application may be having problems, but a number of companies won't support changes to their databases so their hands might be tied as to what they can directly do about it. Being a Developer DBA/Database Architect is much more complex than supporting SQL Servers that have databases for purchased applications.

    Which situation best describes what you are moving into?

    Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
    My Blog | Twitter | MVP Profile
    Training | Consulting | Become a SQLskills Insider
    Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]

  • There are a few Articles on this site that you can use. I remember one call "DBA morning list" or something like that.

  • DBA Morning Checklist -http://www.sqlservercentral.com/articles/Database+Administration/62480/

  • I just wrote one and have a new one coming out on the 12th or 13th. Keep your eyes peeled.

    http://www.sqlservercentral.com/articles/career+growth/64632/[/url]

    ~BOT

  • pavankumarh2 (1/5/2009)


    Dear Friends ,

    I am moving to work on Production support as DBA ,plz any tell me any body what are the common responsibilities of DBA to work on Prod support ,

    Thanks from

    E.Pavan Kumar

    Monitoring database access by privileged users and changes in privileges.

    Check SQL Server Logs, and Security Logs for unusual events. Monitor databases for errors and perform problem determination when necessary.

    Verify that all jobs have run successfully and for failed completion.

    Confirm that backups have been made and successfully saved to a secure location.

    Monitor disk space to ensure your SQL Servers won’t run out of disk space.

    Periodically monitor performance using both System Monitor and Profiler. Monitor performance with PERFMON also.

    Monitor and identify blocking & Waiting issues.

    Verify the Backups and Backup file size and Check Database & Transaction Log Space.

    Verifying Backups with the RESTORE VERIFYONLY Statement

    Manage backup and recovery of databases.

    Optimization and Tuning of Indexes and Code Analysis of procedures.

    Run some DBCC commands (dbcc checkdb / dbreindex / checkcatalog / inputbuffer) to check out database consistency, index fragmentation and Process statement for blocking and waiting and Check DBCC output.

    Maintain database changes from Development, QA and PreProduction to Production for Release process and sync databases from local to production . And also dome Data migration activities from Local server to Production live servers.

    _____________________________________________________________________________________________________________
    Paresh Prajapati
    ➑ +919924626601
    http://paresh-sqldba.blogspot.com/[/url]
    LinkedIn | Tweet Me | FaceBook | Brijj

  • pavankumarh2 (1/5/2009)


    Dear Friends ,

    I am moving to work on Production support as DBA ,plz any tell me any body what are the common responsibilities of DBA to work on Prod support ,

    Thanks from

    E.Pavan Kumar

    Heh... learn how to use Google or other search engine instead of relying just on forums. Learn how to use Books Online. πŸ˜‰

    Although you may think this a sarcastic answer, it is, in fact, a very strong recommendation and is essential to your survival as a DBA. πŸ™‚

    --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)

  • At the risk of sounding flippant, your main responsibilities as a production DBA will be what your company states they are in your new job description. Of course, the various checklists and advice already given above are an excellent starting point and well worth working with, but it's only reasonable for you to be told what is expected of you, and if your company isn't inclined to tell you what they expect of you, I'm not sure I'd want to take on that role yet.

    Semper in excretia, suus solum profundum variat

  • PaulB (1/5/2009)


    Always remember this: DBA owns the structure but never ever the data.

    BWAA-HAAA! For me, anyway... that's not been true. Lose just one byte of data and see who suddenly becomes the owner. Let just one calculation go wrong and the DBA hangs from the same gallows as the developers in a SOX, SEC, or virtually any other data integrity problem.

    Even if the DBA doesn't want to own the data, they frequently do just because. Better ask that question out loud and in writing along with what the other expectations of the position are for the given company.

    --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)

Viewing 14 posts - 1 through 13 (of 13 total)

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