Re: Which method: dblink or import/export?

Paschal,

We went the link route on moving one table (< 1 GB), and it was unexpectedly efficient. However, your network (and database) support groups would probably appreciate you doing the move somewhere other than prime-time, especially if the data volume is great. The link alternative is nice because once the link is set up, it can be reused for movement of other data.

The disadvantage of the link alternative is the overhead of Oracle applying the inserts one-at-a-time. This generates more churn in the rollback areas and index updating processes that a direct load or import.

My vote? I'd go with the link, unless the data volume is large (say,
> 1 GB). Its fast and easy. The most difficult part is setting up
the link, and once that is done the link will be available for later uses.

Patrick Suppes

Paschal Mushubi wrote:

> My task:
> Populating a table in a local Oracle database with
> data from a remote Oracle database:
> Which of these two methods is more efficient for
> transferring large amounts of data?
>
> Using database link:
> PL/SQL procedure opens cursor and selects data from a remote
> database then iserts them into a local database
>
> Import/Export:
> Dump data from a remote table into a dat file
> then ftp it to local machine and use sqlloader to
> insert the data.
>
> Other options?
> Suggestions, please.
>
> Regards.
>
> paschal.
Received on Fri Apr 23 1999 - 11:43:40 CDT