2 Replies Latest reply on Feb 24, 2012 2:11 PM by Anthony.P

    Smartest way to avoid users writing on replica?

      Hi all,

      I'm using Streams uni-directional source -> target at database level. This target DB should be available for all people for query only.
      I've also made some rules to exclude a few schemas from capture. This part works fine, but now, I wonder how people use to avoid users to write changes on the target database (replica).

      I could open it in READ ONLY mode, but in this case, even my DBA user can't make any change (for instance, I'd like to build and run some procedures on this replica, or some developpers may need to create some temporary tables while requesting data).

      So I would like to know how you guys use to "protect" your replicas? (Or maybe my policy is wrong...)