Greetings!
I have doubt about transaction size settings in DB2 stage. It is clear for insert record since one record will be creating one row in database and transaction commit will be according to after rows efined in transaction size. But scenario like delete or update which one record from DataStage end can affected multiple rows in database, how commit is done at DB leve?
eg, I'm update based on a column which is not unique, it means one record of DataStage will affect multiple rows at Database. If I set transaction size at 100, will transaction be committed after 100 records from ETL or every 100 rows affected at DB end?
Hope my explanation is ok.
Looking forward to all comments.
Thanks and Have a nice day!
M
Transaction size in DB2 stage and commit rows
Moderators: chulett, rschirm, roy