asked
Sql server Role
Hi , I am working as a .Net Programmer and also work with SQL Developer, Now i m interested to move to Core Sql Server development area, so I need some clarifications. Can any one tell me ,What are Sql develope role and Sql DBA Role ( What I am expect is , what topics covered to sql developer and what are DBA )
Jaleel, as always "It Depends". If you are lucky enough to work for a company with clear roles, where a database developer only does work on the database engine and no GUI work, then you could take the following points: A SQL Developer would be responsible for the physical database design. They would normally receive a requirement spec and translate this to a database model. This includes table structure (tables, columns, indexes), data access objects (view, stored procedures, functions) and permissions as per requirements (database/application roles and permission assignments). A SQL Dev. that solely works on these objects would liase with the .NET programmer and provide the data access objects to allow the .NET dev to build the application that would interact with the database. The advantage being, a SQL Dev. would learn his craft in more detail and use methods that are not necessarily known to the hybrid .NET/SQL Developer. A SQL DBA would be responsible for the database engine itself. They are responsible for making sure that the database server is kept in order - backups are made of databases, backups are tested, patches are reviewed and installed, system resources are plentiful (CPU, RAM, Hard disk etc), the database system is performing well (monitoring resources and queries). They would also be directly involved with the SQL Developer, helping with design decisions. Quite often the DBA would be called in at the beginning of a project to help highlight possible pitfalls/new technologies that could be used. Ideally, the DBA would have developer experience, to understand how the two roles work. This can sometimes include a third role - Development DBA. This DBA would also take a larger part of the SQL Dev. work. They may be responsible for the architectural decisions (table design etc.) which are then passed to the SQL Devs to be programmed. I hope this helps you understand the differences a little better.
Fantastic answer. Of course, that really only applies to companies that have clear divisions between those roles in many places (all I have experienced personally) the divisions are much more murky.
@TimothyAWiseman - too true, the roles are generally rather fuzzy. I am lucky at my current company. They understand the advantages of this approach and have a pretty good setup. This is around about the 3rd year, and someday soon we hope to get permanent testers too :o)
You might want to check similar questions discussed [here][1] and [here][2] and also [this][3] article from simple-talk website about development DBA. [1]:
http://ask.sqlservercentral.com/questions/2439/differences-between-a-production-and-a-development-dba [2]:
http://ask.sqlservercentral.com/questions/5058/what-topicstools-should-i-need-to-know-to-become-best-production-dba [3]:
http://www.simple-talk.com/sql/database-administration/what-use-is-a-development-dba/
