Re: Audit Journal Entry for Trigger Enable/Disable

Long story short, we use virtual role swap as a way to get a daily refresh.  We replicate some of our production data to an environment on the development machine. Every morning we role swap and let developers use that environment for testing and production debugging.  Every night we switch it back and MIMIX reverts their changes and syncs with production.

A bit Rube Goldberg for my tastes, but it's working for now.  Except for the triggers.  Some triggers access data which is not replicated to development.  So those triggers need to be removed or at least disabled.  I'm not sure if there's a way to tell MIMIX to ignore them for this instance, but I do know how to use the brute force method of modifying the role swap program.

On 5/13/2019 1:59 PM, Rob Berendt wrote:

I would ask Mimix about that.
First thing, we never used the virtual role swap. We just ran the regular swap once a quarter. Did not see the point of the virtual swap. But when we run on the backup machine we do want the triggers to fire.
Never had a problem with the triggers.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Monday, May 13, 2019 2:50 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Audit Journal Entry for Trigger Enable/Disable

Yep, it was D-TG.  And it was MIMIX.

And now I have to figure out how to deal with this.  There are some triggers that we simply don't want on this particular target instance. So I may have to add cod to disable them in our virtual role swap program.  Not the end of the world, but something to consider.