RE: Protecting schema changes

[Richard Ji]

Title: Protecting schema changes

Seperate the object owner from the account which they use to connect.  So they would connect through

an account that doesn't actually own any objects but just have enough privilege to access them.

-----Original Message-----
From: Webber Valerie H [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 10, 2003 2:50 PM
To: Multiple recipients of list ORACLE-L
Subject: Protecting schema changes

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
[EMAIL PROTECTED]
704-566-5321