OUR COMPANY
~65 DATABASE SERVERS(DEV/TEST/PROD/FAILOVER/DR)
A FEW WITH OVER 250 DATABASES ON A SIGLE SERVER.
Total over 2000 databases
3 operations DBAs - responsibilities are maintenance, troubleshooting,
all changes(NOT DEV), backups, restores, replication, security, disk
management, performance tuning, serves on project teams for new
databases or apps that will use SQL server, etc.
and of course helping with sorry code that makes it to production and
THEN causes performance issues.
Development code, database design, and structure changes in dev are
handled by developers and data architects.
Now I must say, although it's a pain when there are things like service
packs to apply to this many servers, we really aren't overloaded. My
opinion is that a single qualified DBA should be able to handle 20-30
servers comfortably as long as they are not required to write code for
developers.
Thanks,
Ralph W. Davis
*********************************************************
*** CORPORATE DBA group - Houston ***
*********************************************************
-----Original Message-----
From: Smith Dano
[mailto:mssqldba-ezmlmshield-x67774479.[Email address protected]
Sent: Tuesday, March 28, 2006 2:49 PM
To: LazyDBA Discussion
Subject: RE: Best Practices
Pertinent info [I think...]
My company
1 DBA, performs all sys-admin [server/network/DR] work and develops
procedures "as-need"
[when developers (10) create performance issues, with cursors 'n
stuff....]
I do schema design for in-house web applications, about 2 per month.
DB's with ~ 10 - 15 tables, and hooks into our "Services"
Create loader apps / scripts to bring in customer data 1-2 MADL -
[Monkey Ass Data Load] per week... Custom / real-quick /....
5 Production SQL Servers, critical DR required !
8 dev/test/uat Servers ... DR is "neglected" SCM used to recover
scripts...
75 Production databases < 10 GB
5 Production databases > 50 GB
We "desperately" need another DBA, but they can be difficult to find...
I think if everyone gave these metrics (servers, DB's, GB of total DB
size) you could guestimate much better.
But every environment is different, so a single dimension will never
tell the story....
If you need regulatory compliance in any way shape or form, add 1 DBA
just to manager Policies/Paperwork....
Dano Smith
-----Original Message-----
From: Michael Everett
[mailto:mssqldba-ezmlmshield-x78443700.[Email address protected]
Sent: Tuesday, March 28, 2006 3:00 PM
To: LazyDBA Discussion
Subject: Best Practices
Importance: Low
Hello everyone,
Can someone point me in the right direction? I am looking for
documentation that sets "guidelines" for the ratio of SQL DB servers to
DBA. We are trying to justify the need for an additional DBA in our
company.
Thank you all in advance.
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
Confidentiality Note: The information contained in this message, and any
attachments, may contain confidential and/or privileged material. It is intended
solely for the person or entity to which it is addressed. Any review,
retransmission, dissemination, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and delete
the material from any computer.
MS Sql Server LazyDBA home page