November 4, 2001 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/bknight/dbaroles.asp
Brian Knight
Free SQL Server Training Webinars
November 5, 2001 at 7:41 am
Brian,
Great article. One which I will use to now define my job better with management. Just hope that the "Hybrid" title does not stick in the industry. Maybe their should be a discussion to come up with something flashier?!.
David
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
November 5, 2001 at 11:42 am
My production team does all the tasks you mention for production. We also work with, but do not have the primary responsibility for, all the tasks you mention on the development side. We are a large Site so the division is natural and works well most of the time.
Some of the Development DBAs will work on a production DBA task from time to time, but their funding is project specific so they tend to have a much narrower focus than the production team does.
We have other contracts that we support that are much smaller than our main IT contract. In the small shops hybrid DBAs are more common. Of course those environments tend to be more chaotic since they often lack formal change control. Configuration management is left up to the individual technical person doing the work. Generally, nobody checks the work of a hybrid. This can be cheaper in the short run, but generally costs more in the long run as each generation of "hybrid" cowboy gets to figure it all out all over again.
November 5, 2001 at 1:10 pm
I like the article. We need a standard view of our jobs for it to be more accepted in all industries.
I think that the production DBA should report to an operatiosn person becuase it forces the development group to adhere to better change control and separates the environment. This is like the QA person reporting to the development manager - BAD idea. People are pushed to short one area to advance another.
Problem is that in too many places, the division is by application or department rather than job title.
Perhaps PASS can help to create, define and advocate some standard roles for SQL Server
Steve Jones
November 6, 2001 at 5:34 am
quote:
Perhaps PASS can help to create, define and advocate some standard roles for SQL Server
I like the idea. The notion that nobody checks the work of a hybrid can be countered by peer-review committees. Each of us at my company works in a small project-driven team. Each person knows everything the other is doing so they can effectivily back each other up. The goal there is to hopefully catch most of what you're speaking of. For smaller companies that can do this though, this can be a concern. Some check would be needed possibily from an architecture person. Great comments!
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars
November 6, 2001 at 10:47 am
I would like to see PASS take a stab at the staffing level issue. Once you define DBA then please provide some guidance on how many an organization should have. A complex but worthy subject!
November 6, 2001 at 11:08 am
brian,
perhaps PASS would create an after hours forum at the conference on this? Maybe a poll?
Steve Jones
November 6, 2001 at 12:18 pm
These would be great topics. I've sent a message to the PASS board members.
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars
December 10, 2003 at 1:01 pm
I like where you are going with this. I work in a small MIS shop supporting a collections center for a large bank. We started using SQL server a couple years ago to replace some of our Access db that outgrew that platform. The management team was of the opinion the SQL server did not need a formal DBA and started building databases as if they were still in Access, each project had its own database and was owned by virtualy all team members. Security is a nightmare, there is very little documentation and we have since built 5 more servers with only a general "idea" of how we would like the environment to look.
I would like to see this discussion expanded to try and define the various roles involved in building/supporting SQL server applications.
I'll stop here so this doesn't turn into a rant about my current environment.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply