Transaction size in DB2 stage and commit rows

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
myotoo
Participant
Posts: 17
Joined: Sun Dec 04, 2005 11:19 pm

Transaction size in DB2 stage and commit rows

Post by myotoo »

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
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

It would be for every '100 records from ETL'. It's all about the requests sent down the link regardless of what that turns into in the actual database.
-craig

"You can never have too many knives" -- Logan Nine Fingers
myotoo
Participant
Posts: 17
Joined: Sun Dec 04, 2005 11:19 pm

Post by myotoo »

Thanks for the answer. Will change it to resolved.

M
Post Reply