Re: Trigger techniques

[Alan Campin <alan0307d@xxxxxxxxx>]

Have you looked at my Trigger Mediator at www.think400.dk/downloads.htm?

The problem with triggers is that they have a read lock on the program. No
way to get them off expect kicking everyone off.

Using the mediator, you just rename the existing version of the trigger
service and go in and update the control and everyone has the new version
instantly. The same thing with turning the trigger on and off.

We are just finishing working on a huge project that using the mediator to
map data from our existing legacy system to new generation tables defined in
SQL.

The challenges have been many, mostly trying to take garbage data from
legacy and map to clean database, but the trigger mediator is working well.

The version on the web is a bit dated. I have added some new capabilities
that I have not posted yet but the basics are there.

If you want me more information, please let me know and I can provide some
assistance. There is a readme with a lot of information on problem in the
package.

On Wed, Apr 7, 2010 at 4:14 PM, Jon Paris <Jon.Paris@xxxxxxxxxxxxxx> wrote:

> Anyone care to share what they do to facilitate being able to bring a
> new version of a trigger program into use.
>
> For performance reasons we don't want to set on LR on each call - but
> how do you make sure that it gets refreshed when a new version is
> available? I can think of a number of options but each one I come up
> seems to have its own issues.
>
>
> Jon Paris
>
> www.Partner400.com
> www.SystemiDeveloper.com
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.