Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Speeding up a Trigger

2 posts in Trigger Last posting was on 2004-11-18 00:23:33.0Z
Jared Sherman Posted on 2004-11-13 05:32:24.0Z
From: "Jared Sherman" <Jared.Sherman@ndchealth.com>
Newsgroups: Advantage.Trigger
Subject: Speeding up a Trigger
Date: Fri, 12 Nov 2004 22:32:24 -0700
Lines: 22
Organization: NDCHealth
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: 204.235.245.20
Message-ID: <41959cf1@solutions.advantagedatabase.com>
X-Trace: 12 Nov 2004 22:34:41 -0700, 204.235.245.20
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!204.235.245.20
Xref: solutions.advantagedatabase.com Advantage.Trigger:138
Article PK: 1136206

Out of curiosity I was wondering if any of the different types of triggers
were any faster than another. Basically I have a large number of update
statements that are going to be fired off in succession. Each of these
updates will cause my update trigger to fire and performs it's little job.
Currently the trigger is bogging me down instead of taking a minute to
perform 1700 updates it ends up taking me 10 minutes. I am using a "before
update" trigger. I'm assuming this means that the post is going to wait on
me. Would an "after update" trigger speed things up? Would it not wait for
me to finish processing before it continues on to the next update statement?
I doubted it would, but I figured I'd ask the pros.

--
_______________________
Jared Sherman
Software Engineer
NDCHEALTH
Physician Services


"Chuck Vertrees \(ADS Marketing\)" <chuck.vertrees Posted on 2004-11-18 00:23:33.0Z
From: "Chuck Vertrees \(ADS Marketing\)" <chuck.vertrees@extendedsystems_removespam.com>
Newsgroups: Advantage.Trigger
References: <41959cf1@solutions.advantagedatabase.com>
Subject: Re: Speeding up a Trigger
Date: Wed, 17 Nov 2004 17:23:33 -0700
Lines: 34
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 192.168.30.179
Message-ID: <419bec18@solutions.advantagedatabase.com>
X-Trace: 17 Nov 2004 17:26:00 -0700, 192.168.30.179
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!192.168.30.179
Xref: solutions.advantagedatabase.com Advantage.Trigger:139
Article PK: 1136204

Jared-

The trigger type won't affect the speed, but turning off implicit
transactions should help.

Chuck

"Jared Sherman" <Jared.Sherman@ndchealth.com> wrote in message
news:41959cf1@solutions.advantagedatabase.com...
> Out of curiosity I was wondering if any of the different types of triggers
> were any faster than another. Basically I have a large number of update
> statements that are going to be fired off in succession. Each of these
> updates will cause my update trigger to fire and performs it's little job.
> Currently the trigger is bogging me down instead of taking a minute to
> perform 1700 updates it ends up taking me 10 minutes. I am using a "before
> update" trigger. I'm assuming this means that the post is going to wait on
> me. Would an "after update" trigger speed things up? Would it not wait for
> me to finish processing before it continues on to the next update
> statement?
> I doubted it would, but I figured I'd ask the pros.
>
> --
> _______________________
> Jared Sherman
> Software Engineer
> NDCHEALTH
> Physician Services
>
>
>
>
>