Re: Export or Ascii Dump for Archiving?

Doing this will not get your referencial integrity straight. Consider that in the example of wanting the data in a different tablespace you could do this by creating the user (data owner) ahead of time and assigning his/her default tablespace to be whatever tablespace you want the data. When the export tries to dump the data into tablespace a and tablespace a doesn't exist, it will put it into the owner's default tablespace.

For very small things, an ascii file might be OK, but I wouldn't try it if you have any referential integrity in your db.

--
Dave A


"Tom Best" <tombest_at_firstusa.com> wrote in message
news:8q7i34$685$1_at_nnrp1.deja.com...


> When you want to archive off some tables from the operational database,

> it seems to me that doing an ascii data dump (usable by sqlldr) makes

> more sense than using export.  I think this because you may not want to

> load it back into the same database with the same tablespace name,

> etc.  The environement you end up loading it back into (for looking at

> for a day, for instance) may be totally different than the operational

> environment it was archived out of.

>

> Do you agree with this?

>

> Thanks,

> Tom Best

>

>

> Sent via Deja.com http://www.deja.com/

> Before you buy.