Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Roles and Responsibilities of Different Teams When Supporting SQL Server Expand / Collapse
Author
Message
Posted Tuesday, June 26, 2012 3:10 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 23, 2012 1:39 AM
Points: 2, Visits: 11
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 :)
Post #1321100
Posted Tuesday, June 26, 2012 3:58 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 12:12 PM
Points: 15,517, Visits: 27,896
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. 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
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1321117
Posted Tuesday, June 26, 2012 5:31 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,068, Visits: 4,639
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.
Post #1321154
Posted Wednesday, October 10, 2012 2:01 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 23, 2012 1:39 AM
Points: 2, Visits: 11

Thanks Paul and Grant :)
Post #1370748
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse