Re: Commitment Control Overhead

[Bob Larkin <blarkin@xxxxxx>]

Karen Bellecci wrote:

> Can someone steer me in the direction of statistics about using Commitment 
>Control.  I have only found the Advanced Backup and Recovery text talking 
>about CC, so far.
> <SNIP>

> What other things do I need to factor in?   Is something published on this?
>
> Thanks.  Karen Bellecci

My attitude is, get faster hardware if the performance hit is unacceptable.
Your example was using two records in a logical unit of work. In my experience, 
there are many more records involved in a LUW. Usually, a Header and many 
Detail records. Rollback processing may be a slight hog, but we usually write 
code with the assumption that the transaction will run to completion.

Another factor is record locking. Every record affected is locked until a 
Commit or Rollback is performed. This is great! Or is it Bad? Depends on how 
you design your application.

I think one of the neatest features is the ability to undo everything with one 
statement by performing a Rollback.

Another added benefit is Journaling (of course you must journal to use CC, but 
not vice versa) A journal can be a fantastic tool if you need to find out 
where/when a record changed. THe journal can provide a wealth of information 
for tracking down problems.

M2cw,
Bob
begin:          vcard
fn:             Bob Larkin
n:              Larkin;Bob
org:            <A HREF="HTTP://web.wt.net/~blarkin/">Larkin Computer Consulting</A>
adr:            <A HREF="http://web.wt.net/~blarkin/">Bob and Diana's Page</A>;;;Houston;TX;<A HREF="http://web.wt.net/~blarkin/">;United States
email;internet: blarkin@wt.net
title:          Systems Consultant
note:           <A HREF="http://web.wt.net/~blarkin/">
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard