Sorry, of course not, it sets the column in IND.
Originally posted by ales
ALTER INDEX NOLOGGING really sets the NOLOGGING column in TABS to "NO".
I'm saying that:
In case of direct-load INSERT, a table with nologging and its indexes with nologging generates significantly more redo than a table without indexes with nologging.
In other words:
In case of direct-load INSERT, indexes on the populated table generate significant amount of redo regardless of their NOLOGGING status.
Click Here to Expand Forum to Full Width