Re: Trigger to SQLServer DB

["Joe Sam Shirah" <jshirah@xxxxxxxxxxxxx>]

    Hi Ivan,

    As I responded to Csaba Kabai a few days back, the trick with triggers
is to do as little as possible, otherwise your processing really gets bogged
down.  That would be particularly true in your case where a database on
another machine must be updated.

    While most people on this list, understandably, look to data queues, I
prefer message queues for their persistence and integrity.

    We have a client application in which the database is updated, usually
by a "C" program from a PC.  Certain transactions must have a fax sent out.
We have an RPG trigger that just grabs the key information and sends a
message to the appropriate queue.  A threaded Java program polls the
message queue every x seconds.  When a message arrives, the Java
program determines if the candidate fits the criteria and performs the
appropriate processing.

    This kind of asynchronous processing, whatever the vehicle, is usually
the best way to go for anything that does not absolutely have to be done in
real time.  HTH,


                                                  Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?             http://www.jguru.com/faq/Java400


----- Original Message -----
From: "Ivan Hurtado" <iva030@xxxxxxxxx>
To: <JAVA400-L@xxxxxxxxxxxx>
Sent: Monday, April 05, 2004 11:00 AM
Subject: Trigger to SQLServer DB


> I need to set up a connection from the iSeries to a
> Windows box running SQL Server. I then have to set up
> a trigger on a table in my iSeries that will execute
> sql insert statements into the SQL Server database.
> Can anyone help?
>
> Thanks,
> Ivan
>