Re: SQL DBA per Server
- From: Lito <Lito@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 7 Oct 2009 09:14:02 -0700
Data Warehouse Architect
"Abba" wrote:
What is DWA?.
"Lito" <Lito@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:28B2129E-A88F-4203-87D8-1F9966C8750C@xxxxxxxxxxxxxxxx
What tool do you use when checking for the diff before checking it in?
How
often they write new codes? How do you move/test stuff from development >
staging > production? How often do you get overruled by your boss
(bypassing
the staging part of deployment)? These are the numbers you need to write
down and divide that by the number of hours you are wearing DB
Developer/Architect hat in addition to the time you spent wearing your
Production DB hat. I was in the same predicaments many times in my career
and it was very draining fighting an uphill battle (in addition to the
fire
you have to put out). I am now wearing only DWA hat and love every minute
of
it ;-)
Lito
"Geoff N. Hiten" wrote:
Sounds like you need a development data architect, not a production DBA.
Maybe a Data QA person as well.
My advice is to take some vacation time and they will figure out just how
much they need you.
--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP
"brymer28303" <brymer28303@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2562D64F-8C95-4723-B0CB-EF287CA88702@xxxxxxxxxxxxxxxx
Most of my day is spent firefighting. We have 7 developers with little
db
programming backgrounds. Technically, I am suppose to QA all db stuff
before
it is moved into production, but that really doesn't happen. I am the
bottleneck. Since our director comes from a programming, he over rules
most
of my suggestions and moves code into production no matter how bad
including
cursors versus using temp tables.
I have alerts set up on most everything from cpu utilization to disk
space.
However, finding time to diagnosis the issue is a problem. The
maintenance
task are pretty automated from full and incremental backups to updating
stats.
Out of our 64 sql servers, 4 are data warehouses which run ok, until a
nightly load fails.
Lastly, I have 3 Oracle servers.
I am just looking for some numbers to support my request that I need
help.
"Geoff N. Hiten" wrote:
As Uri said, "It depends.
Are you firefighting all the time?
How much of your "routine" tasks have you automated?
Do you have time to tune and improve the systems?
60 systems is a lot of servers to handle without some type of
automation.
Have you looked at SQL 2008 Central Management Server and the Codeplex
Enterprise Policy Management project?
(http://www.codeplex.com/EPMFramework)
Automate the routine, get the fires under control, and 60 may not seem
like
so much. I would get a second DBA if you want to take some vacation
time.
--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP
"brymer28303" <brymer28303@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E920901A-3A93-45BA-AB23-E7C3E4B5BAD9@xxxxxxxxxxxxxxxx
Is there any stats showing how many databases and sql server that a
dba
can
handle. I have 60 sql servers and I'm drowning. In requesting
assistance,
our HR wants to know "how many" DBAs does it take? Does anyone know
of
any
published studies?
- Follow-Ups:
- Re: SQL DBA per Server
- From: Abba
- Re: SQL DBA per Server
- References:
- SQL DBA per Server
- From: brymer28303
- Re: SQL DBA per Server
- From: Geoff N. Hiten
- Re: SQL DBA per Server
- From: brymer28303
- Re: SQL DBA per Server
- From: Geoff N. Hiten
- Re: SQL DBA per Server
- From: Lito
- Re: SQL DBA per Server
- From: Abba
- SQL DBA per Server
- Prev by Date: Re: Optimization Job failed.
- Next by Date: Re: Changing Server Name and Domain
- Previous by thread: Re: SQL DBA per Server
- Next by thread: Re: SQL DBA per Server
- Index(es):
Relevant Pages
|
Loading
