Comments on: How often should I commit? http://prutser.wordpress.com/2009/04/28/how-often-should-i-commit/ By: Harald van Breederode Sat, 18 May 2013 15:01:01 +0000 hourly 1 http://wordpress.com/ By: Smurf http://prutser.wordpress.com/2009/04/28/how-often-should-i-commit/#comment-142 Sun, 03 May 2009 09:44:58 +0000 http://prutser.wordpress.com/?p=345#comment-142 Hi Harald,

Are you going to write about MySQL too, now Oracle is also owner of that wonderful database?

Smurf

]]> By: Jaap van Lelieveld http://prutser.wordpress.com/2009/04/28/how-often-should-i-commit/#comment-141 Thu, 30 Apr 2009 19:53:37 +0000 http://prutser.wordpress.com/?p=345#comment-141 I generally agree on your arguments. There is one thing I’d like to add though. Check if the business is aware of what they are asking for. This might help you to find the easiest and cheepest route to a solution. My statement is: a business riquirement should never be translated to a DB “statement” on a 1:1 bases. It is my experience the business is not aware of what they are asking for in terms of DB consequences and performance.
Jaap

]]> By: Gary http://prutser.wordpress.com/2009/04/28/how-often-should-i-commit/#comment-140 Tue, 28 Apr 2009 23:25:31 +0000 http://prutser.wordpress.com/?p=345#comment-140 Some variations on this, especially in the old fahioned batch world.
You may have a file with hundreds or thousands of business transactions. You don’t necessarily need to commit each one individually. In the ‘old’ days, you might batch them up and commit them every few hundred to speed up processing (ie reduce waits on the log writer). In newer versions, you can use COMMIT WRITE BATCH or COMMIT WRITE NOWAIT to have the same effect.

]]>