Re: moving to Oracle need recomendations...

David,

Thanks for the suggestion, I'll check that out as I continue to familiarize myself with this stuff. Always looking for something that might make it easier. I was given a rather limited time to pull this all off so I am already wondering how I am going to be able to do it. It will probably take me longer than what others have allotted for this project (when doesn't it). Anyway I have some idea now and as I continue to read up on all of it I am beginning to see why every one was so strong in their suggestions about *NOT* porting the code and what not. I still have a steep hill ahead but I am starting to make visible progress on all of this.

Thanks again for the suggestion.

--
Regards,
Bill
"David Cressey" <david_at_dcressey.com> wrote in message
news:Sbhr9.192$0I3.16371_at_petpeeve.ziplink.net...


> Bill Lucas,

>

> I'm late to the party on this topic, so I'm sorry if my comments are

out of


> place.

>

> A few years back,  I had to work on transferring data and data

definitions


> from DEC Rdb databases to Oracle databases.  DEC Rdb was actually

bought out


> by Oracle in 1994, and now known as "Oracle Rdb".  But it's still

quite


> different, internally, from "Oracle classic", and should not be

confused


> with what everyone knows as "Oracle".

>

> Anyway,  one very convenient vehicle for moving the metadata was a

component


> of Power Designer called "Data Architect".  It had facilities for

reverse


> engineering a data model from an Rdb Database,  and then converting

the


> model from Rdb product specific to Oracle product specific,  and

then


> generating a create script.  It sure took a lot of the dog work out

of the


> conversion.  My expectation is that  a conversion from SQL server

would be


> just as easy for DA to help with.

>

> This doesn't address migrating the data,  migrating the application

code, or


> familiarizing yourself with the concepts.  Migrating the data was

even


> easier than migrating the model.  Migrating the application turned

out to


> involve a lot of rewriting at the same time,  so the issue became

moot.  And


> changing your head set is probably the hardest part of the

migration.


>

> Good luck.

>

>

>

>

>

>