Toralf Kirsten wrote:
The not logged behaviour needs to be activated per transaction.
Issue ALTER TABLE ... ACTIVATE NOT LOGGED INITIALLY, then logging
will disabled until a commit is issued. After that updates against
that table will be fully logged again.

Caution: if the not logged update fails, your table will become
unavailable (rollback requires logging in DB2)

If you don't want to use NOT LOGGED, take a look at the row_number()
function, you should be able to use it to split up your insert in
smaller chunks.

Regards,
Miro

Thanks Miro,
I'm not really sure what do you mean with row_number().
I know this function and have used it in some cases before.
I'm looking for a high performance solution to insert this large amount
of data.
Do you think I should split the the numbers like this:
insert into ...
select ...
from (select row_number() over() as rn, ...
from ...
where ... ) temp_view
where rn < 200000 and ...
Do you know what happens when I apply th same query but changed the
where clause w.r.t. rn "<"/">" number? Does the database engine carry
out the whole query at first time and apply then where clause conditions?
Ahoi, Tori

miro flasza wrote:
<snip>