Malcolm Dew-Jones wrote:
> Sybrand Bakker (postbus_at_sybrandb.demon.nl) wrote:
> : On 2 Jul 2005 14:22:07 -0700, "Mark D Powell" <Mark.Powell_at_eds.com>
> : wrote:
>
> : >Where there are concurrent DML operations against a target table then
> : >holding a row lock for the duration of a long running update task may
> : >be very undesirable. It should be acceptable for a batch process to
> : >wait a few seconds for a row, but even a two second wait may be two
> : >long for an OLTP user. You have to balance the two competing needs.
>
> : Sure, long-running updates ---> outside office hours.
>
> Assuming you can wait for the weekend for 36 hour jobs.
If you have a 36 hour job then you almost undoubtedly have a design
problem.
--
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Sun Jul 03 2005 - 12:35:08 CDT
