Splitting production and development/test at the DBA level?
- From: "Michael Kline" <mkline1@xxxxxxxxxxx>
- To: "Oracle-L" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 18:17:30 -0500
I've got a client that is considering splitting devl/test and production at the
DBA level.
There are only about 8 Oracle folks, and that would put 6 on Production and 2 on
test and there are about 70-80 databases.
This all has something to do with a Gartner paper that was some 7-8 years old.
Has anyone tried this before and what were the results?
Migrating new code forward just sounds like it will be horrible because now TWO
DBA's will be involve and probably be almost totally unaware of what's coming
and the like.
The strange thing is, this client is into "pools" big time where you get a DBA
from the pool to work on what ever. That is pretty much how they were doing it
now. Yet, being "in line" with this pools thing, they now want to make two pools
and then make it so prod would have no access to devl/test and devl/test will
have no access to prod. It reminds me of like WalMart type stores. "Sorry,
that's not my department." It's got the DBA department quite concerned.
The paper was supposed to say this was the thing to do, and perhaps would make
SOX happy.
Michael Kline
13308 Thornridge Ct
Midlothian, VA 23112
O: 804.744.1545
Fax: 804.763.0114
Other related posts:
