Subject | More bulk loader - sorted data |
---|---|
Author | Bill Oliver |
Post date | 2007-11-10T14:33:19Z |
Hi all,
I often see cases where data to be bulk loaded is pre-sorted. After
the bulk load an index will be created - either a primary key or maybe
a unique constraint.
Would it be helpful to tell the bulk loader that the data to be loaded
is pre-sorted by some column?
Ideally, this information could be leveraged to make creation of index
quicker.
I had a case recently where 30,000,000 rows were inserted into Vulcan
table, and creating the PK took 30 minutes. The data for the PK column
was already sorted and unique.
Don't know if this information would be useful or not. Opinions?
-bill
I often see cases where data to be bulk loaded is pre-sorted. After
the bulk load an index will be created - either a primary key or maybe
a unique constraint.
Would it be helpful to tell the bulk loader that the data to be loaded
is pre-sorted by some column?
Ideally, this information could be leveraged to make creation of index
quicker.
I had a case recently where 30,000,000 rows were inserted into Vulcan
table, and creating the PK took 30 minutes. The data for the PK column
was already sorted and unique.
Don't know if this information would be useful or not. Opinions?
-bill