Re: Table copy via dblink

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: 14 Feb 2006 07:17:13 -0800
Message-ID: <1139930233.865474.24570@g14g2000cwa.googlegroups.com>

Gerald, is this a one time deal or is this process going to be repeated? Also is the target database production or test?

If it is a one time deal either method CTAS or create followed by insert/append is just as good. If you are going to repeat the data transfer then I would suggest creating the table only once so insert/append. I would create a task that truncated the table then re-inserted the data.

If the target is a production database do you really need to use nologging? Seven million rows with short to moderate number of columns will not be very many megabytes. Unless the plan would be to refresh the table on recovery I would want to be able to forward recover the other database. You cannot forward recover an object involved in a nologging operation.

HTH -- Mark D Powell -- Received on Tue Feb 14 2006 - 09:17:13 CST