Re: management paranoia about 2 million rows updated in 1 commit
- From: rjamya <rjamya@xxxxxxxxx>
- To: oracledbaquestions@xxxxxxxxx
- Date: Wed, 22 Aug 2012 11:53:18 -0400
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@xxxxxxxxx> wrote:
> any suggestions on what to say?
--
//www.freelists.org/webpage/oracle-l
Other related posts:
