Re: Reverse engeneering Oracle

Hi Fred,
Robert is absolutely right. The development of a database should be a process that also garantuees a documentation of all objects.

roland

RTProffitt_at_beckman.com wrote:

> Fred,
> I would think that whatever tool you use,
> whether Designer 2000, or ERwin, or something else...
> that if you go to all the trouble to put the database
> into a tool and then improve the database, that you would
> want to move forward into managing the database from
> the tool. That means that in the future, it would
> not be just one time, but ongoing.
>
> We had a circumstance where the vendor was allowed
> to keep changing the database and the DBA was constantly
> playing catch up with the modeling tool. It was a
> nightmare!!! Finally we were able to get strict,
> lock down the databases and enforce a rule: "One direction
> only" All changes will go through the model first and be
> "pushed" out to the databases under our careful control
> and supervision. The database was stabilized, the App
> crashed less due to spurious changes to tables, and
> migrations of changes were made in controllable, logical,
> stepwise fashion. Finally we had a model
> we could trust, test against, play with, etc.
> It was a hard fight, but well worth it.
>
> Everyone hates to be strict and heavy-handed,
> but sometimes it is best in the long run to have
> strict standards!
>
> So, my advice is to look at the long term,
> and decide how the modeling tool will fit in
> with your management of your database...not just
> the immediate cleanup and re-design.
>
> Robert Proffitt
> RTProffitt_at_beckman.com
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
Received on Thu Jun 24 1999 - 21:17:54 CEST