Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Protecting schema changes

Re: Protecting schema changes

From: <Reginald.W.Bailey_at_jpmorgan.com>
Date: Fri, 10 Jan 2003 13:35:05 -0800
Message-ID: <F001.0052CE3E.20030110133505@fatcity.com>

We faced a similar problem. We use change control to help manage this. The developers have the schema password in development , but not in UAT
(Certification) or Production. We create a run-time userid for their
application to use rather than logging in as the schema owner. The run-time userid has all of the necessary rights on the schema' objects, needed for the application. As for changes to the schema, we expect them to send us the DDLs after they have made any changes, with the understanding that if their is a problem we will send it back for corrections or correct the database object ourselves and tell them why the change was necessary. We distribute developer guidelines to them to follow concerning naming conventions, how to access the database , how to access the schema' objects properly, and to never , ever hard-code userids and passwords into their code, unless they wish to die a painful death.:) We also refuse to let them out of the development environment to the UAT environment until the necessary changes are done to correct any problems.

RWB Webber Valerie H <Valerie.H.Webber_at_irs.gov>@fatcity.com on 01/10/2003 01:49:40 PM

Please respond to ORACLE-L_at_fatcity.com

Sent by: root_at_fatcity.com

To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc:

In a n-tier system that connects to the database with JDBC, how does a DBA keep developers from modifying the application schema without the DBA's consent or knowledge in a centralized development environment?

The developers can have their own personal database on their desktops to program/test with but we have a problem with them making changes to the main development database as the application schema owner. They know/have the application schema username/password since it is used to make the JDBC connections to the database from the app server.

Does anyone have links to defined change control processes that might help?

Thanks in advance!
Val

Valerie H. Webber
Management Systems Designers, Inc
Database Administrator
valerie.h.webber_at_irs.gov
704-566-5321

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: 
  INET: Reginald.W.Bailey_at_jpmorgan.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L

(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Fri Jan 10 2003 - 15:35:05 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US