Hi All,

I wanted to ask a basic question. What is the role of auto-commit. Does it automatically commit after every SQL run or it does commit when the UOW(consisting of many SQL) gets over. what is the performance impact and

how to set it off..

I have tried using
db2 update command options using c off
but when I am doing the "list command options" its not reflecting there.

Do I need to do something else.??

autocommit means a commit after each statement
you could also do : db2 -tcvf infile

but there are soo many SQLs to run so i wanted to set it on the system level only. there is something on systme/database level where i can set it for every SQL to run

do you want it on or off
on is default - off means rollback if any error and locks are held
you could modify the db2setcp.bat file that opens the db2 command window and have the setting modified when opening the window

Every serious database application turns auto-commit off because it has a few nasty implications:

• every commit puts some work on the database server because DB2 must at least flush the log records for the committed transaction to disc (unless you can use group commit)
• cursors must be opened as holdable - more resources are needed in DB2 to keep cursor state and implicit cursor-closing and EOT is not available