The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact email@example.com.
One option that comes to mind would be to have the trigger program(s)
simply write the data or the record keys to a data queue.
This is fast for the trigger.
Then you have program(s) that just monitor new entries on the data queue
and process them against the Windows SQL Server.
And if the queue is not being processed fast enough then increase the
number of monitoring programs.
From: "K Crawford" <kscx3ksc@xxxxxxxxx>
Date: 02/09/2022 04:51 AM
Subject: SQL database on window updated by iSeries
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
I have several tables on my iSeries. These tables are replicated on a
Windows server in a SQL database. On the iSeries when the table is
write/update/delete a trigger is activated to do a similar action on the
SQL database using RPG/SQL. This works great, but when a program is doing
lot of updates it gets slow.
Is there a better way to do it? preferably no cost.
We did have the .Net programs direct connect to the iSeries and get the
data, but the number of connections were overwhelming.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.