Re: SQL Triggers - Never Worked With Them

Couldn't be any faster. Write to data queue is virtually instantaneous so
only overhead is the call to the trigger. The one issue is errors. If it can
error out you have to have some mechanism to redo. It gets more complex if
you do not want the update on the AS/400 table to go through if there is an
error updating the SQL Server table. In that case, you have to do the update
in the trigger and throw an error back to prevent the insert or update to
the AS/400 record.


On Tue, Jun 14, 2011 at 11:00 AM, Winchester Terry <
terry.winchester@xxxxxxxxxxxxxxx> wrote:

That's an interesting method...

How is the trigger performance when writing to a
data queue? Is this technique used on high volume
files?

Terry

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Tuesday, June 14, 2011 12:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL Triggers - Never Worked With Them

Why not just do the maintenance from the AS/400? Trigger
fires and writes a
record to a data queue. Never ending server picks up record
and uses Scott's
JDBC API to update SQL Server. We do exactly that with
several projects. Let
me know if you have questions.

On Tue, Jun 14, 2011 at 10:39 AM, Mike Wills
<mike@xxxxxxxxxxxx> wrote:

We have a project now that requires us to sync data between

the i and

a MS SQL Server. I envision a table that collects the table, key(s),
and what action was performed (insert, update, delete). This table
will then be read by a C# program that will then process this table
and copy the appropriate data to the MS SQL Server.

I figured the best way to do this to avoid table changes or program
changes is to use a trigger. I have never personally used or created
triggers and now I am trying to figure out how to insert data into
another table when a trigger is triggered. Is there any
documents/articles/how-tos out there that you recommend to get me on
the right path. Some of the things I have found so far

doesn't really

explain the process well enough that I can figure out how

to create it

myself.

--
Mike Wills
http://mikewills.me
--
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.

--
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.

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains
information that may be confidential, protected by applicable legal
privileges, or constitute non-public information. It is intended to be
conveyed only to the designated recipient(s). If you are not an intended
recipient of this message, please notify the sender by replying to this
message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.



--
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.