Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Roles of development DBA


Roles of development DBA

Author
Message
sql-1017511
sql-1017511
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 71
Hi,

I am new to MS SQL Server. I like to know what are the roles of sql server dba in Development side and in production side.

Thanks
DBA in Unit 7
DBA in Unit 7
SSC Veteran
SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)

Group: General Forum Members
Points: 287 Visits: 1124
In my opinion, Development DBA is like Architect, but would do more detailed design, test, and review codes from Developers (if there is any), if there is no developers, Development DBA may end up in designing the database logical infrastructures and then writing scripts to implement the design. So development DBA should know the business very well and know what the data do in the database.

Production DBA is more like maintening the existing running databases, keeping them up running without issue. Typical Tasks would be: installation SQL Server, backup/restore; engaging with app admins to resolve db-related application issues; disaster recovery strategies work for the business; performance tuning; security administration...etc. PROD DBA is like a housekeeper and firefighter, making sure the DBs are running with high efficieny, availability and redundancy while when there is emergency, should be able to resolve issues swiftly. Production DBA could function well without knowing the business processes/data well.

--(Personally I am a Production DBA)
SQLRNNR
SQLRNNR
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26438 Visits: 18328
I think it largely depends on your company.

Many places they are one and the same. The DBA designs the databse, supports production, and reviews code.

Some places they distinguish between Prod DBA and Development DBA. And in some of those places it only means that the development DBA works more closely on Projects more frequently and has to back up the production DBA.

And yet in other cases, there is a thicker line drawn as to what each group does.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

ChiragNS
ChiragNS
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2853 Visits: 1865
Yup.. depending on the company the roles of development and production dba might overlap.

"Keep Trying"
Silverfox
Silverfox
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3092 Visits: 1161
Depends on the company, I have worked as both production and development DBA.

Development DBA's tend to be more development focused, working with developers, core skills more focused on T-SQL, writing triggers and stored procedures understanding performance tuning. you are expected to know advanced T-SQL and have more knowledge than developers regarding SQL.

Production DBA's more focused on administration of existing systems, keeping them running at peak performance. you generally dont create anything, more support than anything else.

Developers normally graduate into a development DBA role, as it is similiar to what they do normally. Development DBA's dont normally have access to live production servers, that is what Production DBA manage normally.

In some organisations, there are split teams, a development dba team and a production dba team, all with separate sql estates that they manage. but some small organisations, the dba team might manage all environments and be responsible for production servers and development servers as well.

--------------------------------------------------------------------------------------
Recommended Articles on How to help us help you and
solve commonly asked questions

Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden
Managing Transaction Logs by Gail Shaw
How to post Performance problems by Gail Shaw
Help, my database is corrupt. Now what? by Gail Shaw
sql-1017511
sql-1017511
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 71
Thanks for your Replies.
jswong05
jswong05
SSC-Enthusiastic
SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)

Group: General Forum Members
Points: 157 Visits: 476
Query tuning, indexing should be done at least once at dev, at QA before pushing to production environment. The execution plan should be evaluated. If you are serious, you can run Borland stress test in QA to generate traffic effect. It will than be continuous maintained/modified by Production DBA once pushed in production environment. There will be times Production DBA will push code back into development cycle. I have done both roles. "Development DBA bridges developers and DBAs, has to know both sides of work, can slip on either hat". Development DBAs have strength in coding and strength in knowing DB engine. Production DBAs know DB engine and network, storage related issues. Production DBA likely gets rotation schedule of 24x7. Development DBA protects us from falling into a design trap that will causes grief later in production (not bugs, QA dept handles bugs), and saves Developer and DBA arguments back-and-forth.

Jason
http://dbace.us
:-P
SQLRNNR
SQLRNNR
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26438 Visits: 18328
jswong05 (2/26/2010)
Query tuning, indexing should be done at least once at dev, at QA before pushing to production environment. The execution plan should be evaluated. If you are serious, you can run Borland stress test in QA to generate traffic effect. It will than be continuous maintained/modified by Production DBA once pushed in production environment.



Sounds like an answer to a different thread or a very specific corporate method for where you work.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

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