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

MS Sql Server LazyDBA home page