Re: merge into an empty table
Date: Tue, 29 Jul 2008 11:45:14 -0500
No, that table is not partitioned. But I will tell them to populate it via an insert rather than a merge.
"Roman Podshivalov" <roman.podshivalo To v_at_gmail.com> genegurevich_at_discover.com cc 07/29/2008 11:17 oracle-l_at_freelists.org AM Subject Re: merge into an empty table
If your empty fact table is partitioned you can try to exchange partition. That could be the fastest way of populating it.
PS: As of talking developers into changing the ETL code it's not always easy especially in SOX environment 8-(
On 7/29/08, genegurevich_at_discover.com <genegurevich_at_discover.com> wrote: Hello:
My application team is backfilling 150M rows of data from a staging table
into an empty fact table. Under normal condition the fact table will be
populated with the merge from the staging table. This is the first time
load though and there will
be no updates - only inserts. For that reason I think that it should not be
done via a merge, but rather via a straight insert nologging. I believe it will be much faster and more efficient that
a merge (which does an outer join). Am I correct?
http://www.freelists.org/webpage/oracle-l Received on Tue Jul 29 2008 - 11:45:14 CDT