Re: Whats the best way to see what changes have been made to a database structure?

<deanbrown3d_at_yahoo.com> wrote in message news:1108762820.683244.94030_at_l41g2000cwc.googlegroups.com...
> Hi there,
>
> Our small company regularly alters tables, creates new views, adds
> triggers and sequences, and these changes have to be reciprocated at
> out (single) client site. Its hard to keep track, as people forget the
> changes they have made, or don't bother to update files of changes.
>
> What's the best way to compare 2 different schemas in a single
> database? Something that will tell me things like:
>
> 1. This table T1 has a new fields...
> 2. This table T2 does not exist...
> 3. This table T3 has a different key...
> 4. This view is different.
> 5. This trigger is changed.
> 6. This sequence is new.
> etc....
>
> Thanks for any help,
>
> Dean
>

besides the suggestions in the other posts, consider implementing database-level BEFORE CREATE, BEFORE ALTER, and BEFORE DROP triggers to track or manage changes

a simple trigger that just requires a package variable to be set before allowing the operation can serve as a reminder or safety catch in this type of development environment. a more sophisticated trigger can track versions and who did the changes

++ mcs Received on Sat Feb 19 2005 - 05:58:33 CST