SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Roles and Responsibilities of Different Teams When Supporting SQL Server


Roles and Responsibilities of Different Teams When Supporting SQL Server

Author
Message
foreverloops
foreverloops
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 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 Smile
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)SSC Guru (95K reputation)

Group: General Forum Members
Points: 95363 Visits: 33013
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 Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
SSChampion
SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)

Group: General Forum Members
Points: 13605 Visits: 4639
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 Smile


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.
foreverloops
foreverloops
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 Visits: 11
Thanks Paul and Grant Smile
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search