Richard,
A roll your own variety of this shouldn't be too hard
to implement.
What you would need:
A schema to build a mini data dictionary. Meta-data if
you will, but not as complex as the images that term
conjures up.
Store standard info about tables, indexes, columns, views,
storage, sequences,etc. For stored code, just duplicate it
in your mini-meta-data. ( hey, that kinda rolls off the
tongue doesn't it :)
Add columns to your meta data for time series ( dates ),
and revision number.
Take a snapshot ( not to be confused with oracle snapshots )
of the schema, include the current date/time and revision
number on all objects.
You should have another table for storing a row for each
baseline taken, with date, revision number and notes (
is this schema production ready? , etc )
You now have baseline data to compare against a schema. The
SQL to check the differences is not very complicated, just
a little time consuming to write. I've done it before and
it's not too bad.
You will now have a valuable tool for determining if a
schema matches a baseline or not, and will have it done
long before you can get a a purchase order for a new piece
of software to install,license, configure, etc.
Jared
On Tuesday 05 June 2001 11:45, Richard Huntley wrote:
> I'd appreciate any info. anyone could provide on what method you use to
> track database changes that have been implemented in
> dev, test, stage and production. I need a way of tracking frequent
> modifications to tables, packages, etc.. and wanted to get some input on
> how others are handling this.
>
> TIA,
>
> Richard Huntley
> E-mail: [EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).
