PK vs ROWID MV Logs for Fast Refresh MV's
Question: Do PK MV Logs increase performance over ROWID MV Logs for MV Fast Refresh on a joining/aggregating MV?
Oracle recommends PK MV Logs since one can re-org the base table without having to do a COMPLETE REFRESH of the MV, however, are there any performance related factors in choosing one or the other?
A canned application, which does not easily support the creation of PK's/FK's, sits atop the database . All PK's/FK's created to support REWRITE currently have to be dropped and recreated before and after nightwork due to the limitations fo the system. So clearly not having to worry about having to keep PK's in place during nightwork is a bonus.
Oracle recommends PK MV Logs since one can re-org the base table without having to do a COMPLETE REFRESH of the MV, however, are there any performance related factors in choosing one or the other?
A canned application, which does not easily support the creation of PK's/FK's, sits atop the database . All PK's/FK's created to support REWRITE currently have to be dropped and recreated before and after nightwork due to the limitations fo the system. So clearly not having to worry about having to keep PK's in place during nightwork is a bonus.
0