Roles and Responsibilities of Different Teams When Supporting SQL Server

  • Hi,

    I work for an organisation where we have approximately 75 IT staff. We have a development team, an application service team and an infrastructure team who jointly support MS SQL Server. I'm trying to draw up a RACI matrix to show who should do what and I wonder if anyone has any examples they could share?

    I appreciate it will be different at other companies but it would make a good starting point. We tend to follow ITIL in terms of the division of roles. We don't have a DBA at the moment but I will probably be recruiting one shortly.

    I have searched this forum and the web and can't find anything of much use. I have managed to cobble together some roles for SQL Server e.g. backup, performance monitoring etc and who I think is responsible for them.

    I suspect that the roles and responsibilities are similar for other flavours of SQL so please don't be put off if you use Progress or Oracle etc.

    Thanks,

    Matt 🙂

  • You're right, every organization attacks that differently. The best documentation I've seen for laying out roles & responsibilities is an older book called "Database Administration" by Craig Mullins. It's still very applicable to more modern methods.

    In general, I'd suggest you get two roles filled. First, and most important, that of the DBA. This is the person who you'll task with responsibility for your production data. He'll act as gatekeeper & guard on the production systems. That means backups & integrity checks, but also security, disaster recovery, high availability, etc. If he does the job right, he's going to keep your developers out of production (which inevitably leads to fights) and he's going to control and direct reporting & other ad hoc access to secondary systems (either purpose built reporting systems, or QA/test environments).

    I'd suggest getting a second role for database design & development. This person will know how databases work internally. He'll be able to write or tune T-SQL queries, design well structured databases and create deployment processes.

    I outline a lot of the work involved in database development in my chapters of the book SQL Server Team-based Development[/url]. The e-book is a free download.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • foreverloops (6/26/2012)


    Hi,

    I work for an organisation where we have approximately 75 IT staff. We have a development team, an application service team and an infrastructure team who jointly support MS SQL Server. I'm trying to draw up a RACI matrix to show who should do what and I wonder if anyone has any examples they could share?

    I appreciate it will be different at other companies but it would make a good starting point. We tend to follow ITIL in terms of the division of roles. We don't have a DBA at the moment but I will probably be recruiting one shortly.

    I have searched this forum and the web and can't find anything of much use. I have managed to cobble together some roles for SQL Server e.g. backup, performance monitoring etc and who I think is responsible for them.

    I suspect that the roles and responsibilities are similar for other flavours of SQL so please don't be put off if you use Progress or Oracle etc.

    Thanks,

    Matt 🙂

    DBA owns the structure but neither data, code nor infrastructure.

    Business owns the data.

    Development/Applications team owns the code.

    Systems/Networking/Storage team(s) own the infrastructure.

    Digging deeper in DBA responsibilities, DBA is responsible for: Database Integrity, Availability, Recoverability, Security and, Performance.

    _____________________________________
    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.
  • Thanks Paul and Grant 🙂

Viewing 4 posts - 1 through 3 (of 3 total)

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