Looking for docs that would distinguish different DB envs.

[sambavan]

Hi,

I would like to know whether anyone know of any site(s) that had documentation on how open a database needs to be in different statges (DEV/TEST/PROD)? Also looking for some docs in that would define the seperation of duties on different environments?

Something like the software design for the database in specific would greatly be helpful.

Thanx,
Sam

[dbasan]

Mmmm all in one nutshell.

Looking for one, a long time.

[sambavan]

Probably by spinning a discussion, we can come up with one. At this point I couldn't find any document that would give a template on how each environment had to be defined and what privileges that each environment had to provide to the development comunity. I know there are two models, one to start with the all open concept and the other would be the all close. It also depends on the environment. Given these, there are no docs to backup any aregument what needs to be open and not all (DBA privs) to all in an all open environment?

If we can come up with a discussion stage by stage or if you prefer me to spin out a new thread per environment, please let me know I'm all for it.

Thanx,
Sam

[TimHall]

Hi.

You should lock down all your environments, even DEV if possible. If developers have to come to you, hopefully they will actually think about what they want before filling the database up with crap designs and bogus data. Also, the closer the environments are, the less likely you are to get into trouble when moving code from DEV to TEST to PROD.

Oracle released a basic security note:

https://metalink.oracle.com/metalink...&p_id=340009.1

I've summarised the important points here:

http://www.oracle-base.com/articles/...sForOracle.php

As for software design, try these:

http://www.amazon.com/exec/obidos/re...-%2F0072230657
http://www.amazon.com/exec/obidos/re...-%2F0072230657

Cheers

Tim...

[dbasan]

TimHall has done a good job by giving the links to start with Sam.