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 of development DBA Expand / Collapse
Author
Message
Posted Friday, November 13, 2009 12:33 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, January 24, 2010 12:47 PM
Points: 10, 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
Post #818809
Posted Saturday, November 14, 2009 4:39 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, September 8, 2014 2:16 PM
Points: 196, Visits: 1,082
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)
Post #819081
Posted Saturday, November 14, 2009 8:10 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:52 AM
Points: 21,738, Visits: 15,426
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #819091
Posted Monday, November 16, 2009 2:40 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 1, 2014 6:55 AM
Points: 2,366, Visits: 1,845
Yup.. depending on the company the roles of development and production dba might overlap.

"Keep Trying"
Post #819262
Posted Monday, November 16, 2009 4:25 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 5:22 AM
Points: 2,728, Visits: 1,119
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
Post #819289
Posted Tuesday, November 17, 2009 8:47 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, January 24, 2010 12:47 PM
Points: 10, Visits: 71
Thanks for your Replies.
Post #820131
Posted Friday, February 26, 2010 9:35 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Saturday, September 13, 2014 12:30 AM
Points: 27, Visits: 470
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
Post #873536
Posted Friday, February 26, 2010 11:09 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:52 AM
Points: 21,738, Visits: 15,426
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #873602
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse