Re: Difficult migration question

If you develop in 8.1.6 on NT, then you just have to export and then import into the database running on Unix. Pros: same RDBMS version which leads to almost no conversion problems. Cons: if db is large, export/import can take a long time. You'll also need to find and configure two seperate boxes.

If you develop in 7.3.4 on Unix, then you'll have two basic ways of upgrading to 8.1.6 on Unix. One, you can use the migration utility. Two, you can export/import which brings us back to the preceding paragraph. Pros: Only one box to configure. For large db, migration is much quicker than export/import. Cons: upgrading to a new RDBMS version

Personally, I'd go the 1st route. I'd rather move a database from NT to Unix on the same RDBMS version than have to migrate to a new version. But that's just one man's opinion.

HTH,
Brian

Don Hunter wrote:
>
> I have an application that requires the storage of images within the
> database. From what little I know I believe I am best using 8.1.6 as opposed
> to 7.3.4. Unfortunately I will not have 8.1.6 available, on UNIX, until
> later this year.
> I have the option of developing it on an NT platform now in 8.1.6 then
> migrating it to the UNIX platform (my company's approved standard) later
> this year, or developing in 7.3.4, on UNIX, now and migrating to 8.1.6 later
> this year.
>
> What I need is some sort of pro's and con's list, or some documentation that
> will help me determine what is the best approach.
>
> Could someone please point me at any documentation that will assist me.
>
> TIA
> T.D.Hunter
 

-- 
========================================
Brian Peasland
Raytheons Systems at
  USGS EROS Data Center
These opinions are my own and do not
necessarily reflect the opinions of my 
company!
========================================