Commit - standard or guideline

Carl Nelson

Commit - standard or guideline

Does your shop have any statements regarding commit logic/frequency?

Is it a standard or guideline?




Thanks
Carl Nelson
WellPoint Database Architecture
317-287-7222



CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

---------------------------------------------------------------------------------
Welcome to the DB2 User Group - Indiana list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/DB2-UG-Indiana.html. From that page select "Join or Leave the list". The IDUG Listserv FAQ is at http://www.idugdb2-l.org. The DB2 User Group - Indiana List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Dale Smock

Re: Commit - standard or guideline
(in response to Carl Nelson)
Standard: any batch update process that executes during a time that online
users are active must take commits at a frequency that simulates online
activity, and have built-in logic to restart the update process at the last
commit point. We have a DB2 "restart/commit" table that contains a row for
every batch update process with the default commit frequency (allows the DBA
to dynamically change if required). Each update program reads that table to
obtain the commit frequency and updates the row prior to each commit with a
logical key that can be used to determine where to restart the process.



We did have to "grandfather" some existing applications to allow update
without commits, which were designed to run only at night while the online
systems for that application are not in use.



Dale Smock

Random House (BMG)



_____

From: DB2 User Group - Indiana List [mailto:[login to unmask email] On
Behalf Of Nelson, Carl
Sent: Wednesday, May 31, 2006 2:20 PM
To: [login to unmask email]
Subject: Commit - standard or guideline





Does your shop have any statements regarding commit logic/frequency?

Is it a standard or guideline?





Thanks
Carl Nelson
WellPoint Database Architecture
317-287-7222


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise be protected by law. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.
-----------------------------------------------------------------------------
---- Welcome to the DB2 User Group - Indiana list. To unsubscribe, go to the
archives and home page at
http://www.idugdb2-l.org/archives/DB2-UG-Indiana.html. From that page select
"Join or Leave the list". The IDUG Listserv FAQ is at
http://www.idugdb2-l.org. The DB2 User Group - Indiana List Admins can be
reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the DB2 User Group - Indiana list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/DB2-UG-Indiana.html. From that page select "Join or Leave the list". The IDUG Listserv FAQ is at http://www.idugdb2-l.org. The DB2 User Group - Indiana List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm