Path: news.easynews.com!easynews!news.he.net!news-hog.berkeley.edu!ucberkeley!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail
From: Rick Denoire <100.17706@germanynet.de>
Newsgroups: comp.databases.oracle.server
Subject: How to monitor schema changes
Date: Thu, 06 Jun 2002 23:54:56 +0200
Organization: T-Online
Lines: 18
Message-ID: <43lvfuo2shp4rhj2p25nbn2cq38th1m21c@4ax.com>
Reply-To: 100.17706@germanynet.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.t-online.com 1023400491 06 9770 f4o1bqYTSTAr85 020606 21:54:51
X-Complaints-To: abuse@t-online.com
X-Sender: 320058382570-0001@t-dialin.net
X-Newsreader: Forte Agent 1.7/32.534
Xref: easynews comp.databases.oracle.server:149799
X-Received-Date: Thu, 06 Jun 2002 14:52:28 MST (news.easynews.com)

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