I am
curious to know if the NOLOGGING option would work in an update or insert
statement, I mean by using NOLOGGING in an update statement can writes to the
redo log be turned off for a particular update or insert operation for that
matter. Specially for huge updates where heavy log switches are possible
filling up the archive log directory.
Please
let me know if this can be done.
example in a situation where 10 Million rows need to
updated.
update
temp NOLOGGING
set
zip=11003
where
city='Boston'
/
Thank
you
