Re: management paranoia about 2 million rows updated in 1 commit
From: rjamya <rjamya_at_gmail.com>
Date: Wed, 22 Aug 2012 11:53:18 -0400
Message-ID: <CAGurbTNQgwypJV+dKKfKwgnDmrBn4=Wk=zqvOGwk0Vd1aj2HAw_at_mail.gmail.com>
So you dont have a technical issue, but a management issue. I'd still go with single statement update. With multi sessions, batched commits, if it rolls back, you will spend hours ot find which ones were updated and which ones were not for the subsequent runs.
Date: Wed, 22 Aug 2012 11:53:18 -0400
Message-ID: <CAGurbTNQgwypJV+dKKfKwgnDmrBn4=Wk=zqvOGwk0Vd1aj2HAw_at_mail.gmail.com>
So you dont have a technical issue, but a management issue. I'd still go with single statement update. With multi sessions, batched commits, if it rolls back, you will spend hours ot find which ones were updated and which ones were not for the subsequent runs.
Raj
On Wed, Aug 22, 2012 at 11:41 AM, Dba DBA <oracledbaquestions_at_gmail.com> wrote:
> any suggestions on what to say?
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 22 2012 - 10:53:18 CDT