(More if I truncate it in the same transaction as the copy)
If you can't drop the pk constraint, can you at least generate the values in sort-order?
Cheers,
Jeff
No I'll leave the pk in at the very least. My example load (37M records) will not be the last word by any means. That's one experiment, if you will. My goal is not to see how fast I can get records in, rather to see what I can expect going forward.
You will probably want to pre-load the unindexed (including no PK) table with dummy values until you anticipate at least index will be larger than RAM. Then build the indexes and PK; and then load some more values and time that load.
If you just test on a small table, you will get answers that are unrealistic for the long term. If you try to build up the table from scratch with the indexes in place, it could take 6 months to simulate 12 months of growth.
