Developer vs DBA role
Hi,
I would like to know where the fine line normaly goes between a developer and a DB admin.
The situation is that we (the developers) have been asked to do some traditionaly DBA stuff like account management, back-up job's, system supervision, set up new SQL Server instances and so on.
As it is now I do the database design and implement it with sp's, udf and DTS packages after that I code the desktop application/web application.
So what is normal where do DBA end and where do DEV begin ?
I would like to know where the fine line normaly goes between a developer and a DB admin.
The situation is that we (the developers) have been asked to do some traditionaly DBA stuff like account management, back-up job's, system supervision, set up new SQL Server instances and so on.
As it is now I do the database design and implement it with sp's, udf and DTS packages after that I code the desktop application/web application.
So what is normal where do DBA end and where do DEV begin ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't think a large organization would find it financially sensible to have programmers in the production systems. For security and stability reasons alone, it makes sense to not have the people coding also in the live database -- not saying that you'd do anything, but it invites the possibility of unauthorized changes in order to allow certain functionalities to work. Those changes might break other things, etc.
You are 100% correct IMHO. You should not be doing production database changes & maintenance at a large biz, if you are an app developer. The company should pick one role for you (preferably based on your stronger skills) and stick with it.
You are 100% correct IMHO. You should not be doing production database changes & maintenance at a large biz, if you are an app developer. The company should pick one role for you (preferably based on your stronger skills) and stick with it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As I see it everything that is related to development in SQL Server is our territory, like database design, complex stored procedures, user defined functions and tricky data transformation.
Responsibility for the DBA should be to maintain the backups, handle accounts, supervision and perhaps installing scripted databases made by us.
But thats what I think, maybe there is a lot of programmers who do server side administration when the organisation is cut down, but I dont see how I can possibly have time to do this also :)
More input and thought's please.