Path: news.easynews.com!easynews!peer1-sjc1.usenetserver.com!usenetserver.com!cyclone.bc.net!newsfeed.stanford.edu!lnsnews.lns.cornell.edu!paradoxa.ogoense.net!sn-xit-04!sn-post-01!supernews.com!news.supernews.com!not-for-mail
From: Sharon <Sharon@kipnuk.marinliving.net>
Newsgroups: comp.databases.oracle.server
Subject: Re: How to monitor schema changes
Date: Thu, 06 Jun 2002 15:12:45 -0700
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <3CFFDE5D.2C32C3C7@kipnuk.marinliving.net>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
References: <43lvfuo2shp4rhj2p25nbn2cq38th1m21c@4ax.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: newsabuse@supernews.com
Lines: 23
Xref: easynews comp.databases.oracle.server:149802
X-Received-Date: Thu, 06 Jun 2002 15:10:09 MST (news.easynews.com)

I would suggest something called change control

Rick Denoire wrote:

> Hello
>
> Users complain to the DB administrator (me) when the DB developer has
> changed the DB schema so that the SQL queries don't work anymore.
>
> Is there a way to monitor changes in the DB schema? I mean when tables
> or views are renamed, columns are deleted, etc.
>
> I thought that doing an export with the option rows=no and comparing
> this output (which contains all ddl commands) with further similar
> exports should reveal any changes.
>
> In general, what is the best practice in order to avoid this kind of
> problems caused by changes in the DB schema? (Supposing that such
> changes are absolutely necessary).
>
> Thanks
> Rick