Re: Constant Update of SQl Server from an iSeries

You have to write them somewhere in case you can't reach the SQL server.

Direct communication from a trigger strikes me as a bad idea in general.
Consider there's no way to handle a set of changes being rolled back; as
the trigger doesn't get called again. Unless ARDGATE supports distributed
transactions (XA)?

Charles

On Wed, Nov 19, 2014 at 12:05 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

So why create a duplicate file

with all entries just so you can queue up trigger entries?

for the trigger version, you don't need a duplicate file, just write the
changes immediate to SQL Server, ArdGate is fast enough and scales very
well.

D*B
--
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.