November 13, 2009 at 12:33 pm
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
November 14, 2009 at 4:39 pm
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)
November 14, 2009 at 8:10 pm
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[/url]
Learn Extended Events
November 16, 2009 at 2:40 am
Yup.. depending on the company the roles of development and production dba might overlap.
"Keep Trying"
November 16, 2009 at 4:25 am
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.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
November 17, 2009 at 8:47 am
Thanks for your Replies.
February 26, 2010 at 9:35 am
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
😛
February 26, 2010 at 11:09 am
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[/url]
Learn Extended Events
July 26, 2017 at 6:21 am
This was removed by the editor as SPAM
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply