I bounce through a LOT of shops, and here's some average numbers I've seen at successful shops. Mind, this comes under the topic of 'What is a DBA' as well.
DB Developers: 1 for every 3-4 actively coding Scrum teams after initial deployment.
DB Architects: 1 for every actively planning/first deployment application in development.
DB Code Slingers: Day to Day support, cleaning up data load failures, bug fixes, deep optimizations, peer code reviews, etc. 1 per every 0 you add to 100 users. (IE: 100: 1 Slinger, 1000, 2 slingers, 10000, 3 slingers). They're generalists. They MIGHT fall under the developer category, but you usually need floaters to be able to handle the runoff.
DB Administrators: As mentioned above, this will depend on their level of day to day involvement. Assuming that they are not in day to day code but merely maintenance and upkeep, a team of four to six is usually used. Note, not six per x... just four to six. The reason is most of their work is done bulk. The detailed stuff is handled by those listed above. You want AT LEAST four however so that the 'oncall' is at most 1wk/month. Any more then that and it's burnout city. Six is better because then you've got vacation coverage and the like.
A lot of people will wear multiple hats in this hierarchy. For example, your code slingers might double up as architects on new projects, since they usually have more bandwidth, and they've been doing the 'cleanup' work while waiting for a new project to start.
Everything, though, depends on the level of involvement of the DBA at the shop in different projects. So, as usual, on SCC, the answer is... It Depends.
- Craig Farrell
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA