Whoops - rereading this and I notice I state "All will receive I, U and D activity". One responder questioned how I could do this w/RO snapshots. Obviously can't. The point I meant to make is I have to manage an initial population of data and then the changes. Fast refresh would be my preference - hence the logs. So, the method I'm leaning toward is simple RO snapshots w/fast refresh. No updateable snapshots required.
There is overhead (an extra insert at least) on the PROD instance associated w/snapshot logs, likewise triggers if I use them. My question is simply what do others do to avoid this overhead (if anything) when handling incremental DML? I can only assume that in very high transaction environments, the logs/trigger approach would reduce commit time and, in turn, application performance. Does this present concern to some? Any and all comments much appreciated ... and thanks Mark for pointing out my err ... :-) -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Casey Dyke INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
