|
Home > Archive > MS SQL Server > March 2006 > Server Database to DBA Ratio
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Server Database to DBA Ratio
|
|
|
| Hi, I am currently trying to justify another dba for our SQL environment.
Writing down time spent day to day can change and not be an accurate amount
of time.
I am trying to locate any formulas or documentation pertaining to this. It
would contain the following DBA to SQL / DBase ratio etc....
What it really comes down to is to make sure to much workload isn’t taken on
by one employee.
| |
| Keith Kratochvil 2006-03-06, 7:16 pm |
| There is not a right answer to this question. The DBA role in each shop is
different. Different projects cause different workloads on a DBA.
Development, production, maintenance, and troubleshooting all require
different amounts of effort.
If your DBA has bags under his or her eyes they are probably overworked.
Then again, they might have a newborn at home that keeps them up nights.
If your DBA arrives late, takes a long lunch, and leaves early there might
not be enough work to go around.
--
Keith Kratochvil
"RussN" <RussN@discussions.microsoft.com> wrote in message
news:1AF919A0-8E30-41DE-A044- ADAC3574CD6F@microso
ft.com...
> Hi, I am currently trying to justify another dba for our SQL environment.
> Writing down time spent day to day can change and not be an accurate
> amount
> of time.
>
> I am trying to locate any formulas or documentation pertaining to this.
> It
> would contain the following DBA to SQL / DBase ratio etc....
>
> What it really comes down to is to make sure to much workload isn't taken
> on
> by one employee.
>
| |
| Geoff N. Hiten 2006-03-06, 7:16 pm |
| Not to put too fine a point on it, but anytime I am asked to "justify" the
need for another person, I find that such justification is an impossible
task. It is often managerspeak for "no, but I won't really say that word".
If you are a manager, you should have enough information to make and follow
through on a decision. If you are the DBA, your manager should see and
address the workload issue. If you are the overworked DBA, polish your
resume and see what is out there if they won't get you the help you require.
Note, I am not saying to threaten to leave. Ask for what you need and
present a reasonable case. If they turn you down, either decide to stay or
decide to leave. Then act accordingly.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Keith Kratochvil" <sqlguy.back2u@comcast.net> wrote in message
news:Ox0a0JWQGHA.5400@TK2MSFTNGP09.phx.gbl...
> There is not a right answer to this question. The DBA role in each shop
> is different. Different projects cause different workloads on a DBA.
> Development, production, maintenance, and troubleshooting all require
> different amounts of effort.
>
> If your DBA has bags under his or her eyes they are probably overworked.
> Then again, they might have a newborn at home that keeps them up nights.
>
> If your DBA arrives late, takes a long lunch, and leaves early there might
> not be enough work to go around.
>
> --
> Keith Kratochvil
>
>
> "RussN" <RussN@discussions.microsoft.com> wrote in message
> news:1AF919A0-8E30-41DE-A044- ADAC3574CD6F@microso
ft.com...
>
>
| |
| Michael Hotek 2006-03-15, 1:23 pm |
| No formula exists and anyone trying to create one isn't going to have
anything useable. One database that I've worked on at a company requires 4
DBAs for the single database to keep it going and they are all busy. Of
course, it helps that the database has thousands of tables, tens of
thousands of procedures/functions, etc. along with terabytes of data.
I also have one environment where a single DBA manages in excess for 2000
SQL Server instances with more than 15000 databases. When things go wrong,
multiple DBAs help out, but the day-to-day stuff is accomplished by 1 DBA.
Those are extremes in the spectrum.
--
Mike
http://www. solidqualitylearning
.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"RussN" <RussN@discussions.microsoft.com> wrote in message
news:1AF919A0-8E30-41DE-A044- ADAC3574CD6F@microso
ft.com...
> Hi, I am currently trying to justify another dba for our SQL environment.
> Writing down time spent day to day can change and not be an accurate
> amount
> of time.
>
> I am trying to locate any formulas or documentation pertaining to this.
> It
> would contain the following DBA to SQL / DBase ratio etc....
>
> What it really comes down to is to make sure to much workload isn't taken
> on
> by one employee.
>
|
|
|
|
|