We have 17 and it's just me. I work in a large organization where capital
expenditure is usually not a problem. Harder to hire a person than buy a new
server. Hence there is usually one server per database. Apps that are stable
and have no development, I might log into the database once every six
months. So there is really only a few databases that take up all my time. It
seems like the more development/ever changing volumes there is on a
database, the more it takes up my time. A static database requires very
little maintenance.
- Original Message -----
From: "Khemmanivanh, Somckit" <somckit.khemmanivanh_at_weyerhaeuser.com>
To: <DMcGibbon_at_tollnz.co.nz>; "Oracle List" <oracle-l_at_freelists.org>
Sent: Thursday, June 09, 2005 5:37 PM
Subject: RE: databases per dba
>
> Just curious, for those that have so many DBs per DBA -- how to you
> effectively support them all in 1 day? Automation is going to help but
> there are still issues that arise...i.e. performance issues, bugs, bad
> change mgmt practices, users just being users, etc...=20
>
>
> Thanks!=20
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jun 10 2005 - 09:03:00 CDT
