Unless you have a forward thinking manager or someone with budget to spare
and a desire to increase head count, all the rational arguments are going to
be for naught. A crisis is usually the only thing to make something
meaningful happen.

Not that I would suggest or condone this approach, but...

If certain databases were to start to have "issues" on an increasingly
frequent basis, starting with tiny development databases and moving upwards
to mission critical instances until someone takes notice.

If a senior manager has a "pet" database, you might not have to have too
many "issues".


-----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