Re: Erwin reverse engineering question

Thanks for the good suggestions.

Since the destination environment has a radically different data model, all we're concerned with is extracting the legacy data. Renaming the columns and using views may be the best approach.

"Willem Dekker" <willem_at_serc.nl> wrote in message news:9sreta$ibo$1_at_newshost.accu.uu.nl...
>
> "Steve Jones" <steve_at_jones.com> wrote in message
> news:3bf01f65$0$8506$cc9e4d1f_at_news.dial.pipex.com...
> > "Jerry Gitomer" <jgitomer_at_erols.com> wrote in message
> > news:9snkqq$ksc$1_at_bob.news.rcn.net...
> > > Tim Mueller wrote:
> > >
> > > You are best off biting the bullet and renaming the columns.
> > > To minimize hardship on your developers prepare a cross
> > > reference for them with old names and new names.
> > >
> > >
> > > --
> > > Jerry Gitomer
> > > Once I learned how to spell DBA, I became one
> >
> > I believe you can define synonyms in Oracle, for the old names, so the
> > Developers can still use their names without having to change anything.
>
> If you want something more than just new names for tables you can use
views,
> and they are also supported in more databases than only Oracle. Althoug
the
> implementation
> efficiency of views differs in the various database products, how well
they
> can optimize away the views, and allow updates on views.
>
> Willem
>
>
>
>
Received on Thu Nov 15 2001 - 05:47:45 CET