Hi, I have been loading a 500,000 recordset Table in DB2 using (LOAD...REPLACE INTO). It took me about 30 seconds on our robust server.
So, When using (LOAD...INSERT INTO) it will take the same 30 seconds for the first load (loading into an empty table).
When Loading again (Loading into a table filled with 500,000 recordssets) it took so long time that I just gave up after 30 minutes. The Manage Utility of DB2 Control Center shows after half an hour a progress of only 20% with a curent phase (DELETE).
It is obvious, that load command in second senario tries to find duplicates and removes them after loading. I was wondering if there were any option to optimize this terrible drawback!.
Thanks in advacne,
Mustafa Al-Durra
Germany.
So, When using (LOAD...INSERT INTO) it will take the same 30 seconds for the first load (loading into an empty table).
When Loading again (Loading into a table filled with 500,000 recordssets) it took so long time that I just gave up after 30 minutes. The Manage Utility of DB2 Control Center shows after half an hour a progress of only 20% with a curent phase (DELETE).
It is obvious, that load command in second senario tries to find duplicates and removes them after loading. I was wondering if there were any option to optimize this terrible drawback!.
Thanks in advacne,
Mustafa Al-Durra
Germany.