Re: Performance Question - trigger

From: Tyler D. Muth <tyler_muth_at_hotmail.com>
Date: 4 Aug 2002 09:25:16 -0700
Message-ID: <1afec35e.0208040825.49bce7ec_at_posting.google.com>


cvonancken_at_orkand.com (Curtis VonAncken) wrote in message news:<b712ca72.0207300811.709a3ed6_at_posting.google.com>...
> Hey folks,
> I'm hoping someone can help me get a grasp on this. I have a package
> that runs several procedures to delete and then re-populate a table
> that one of our apps uses as an index of sorts. It's a rather complex
> set of procedures and the best I can get the time for them running is
> about 5 mins. That data contained in this table is directly impacted
> by the data two other tables. My first thought is to have trigger
> that will run on update or insert for the two tables.
>
> What I need to know is if say user A runs an update on table xxx (one
> of the two tables) and the tigger runs my set of procedures will this
> affect user A's performance? Note that user A has nothing to do with
> the table and app that trigger affects.
>
> Does the tigger run in the background or is it directly tied to that
> users transaction?
>
> Is there a better way that I should be doing this?
>
> sorry if I made this confusing...

Look into using a Materialized View. Make sure you check out all of the refresh options before discounting it. Received on Sun Aug 04 2002 - 18:25:16 CEST

Original text of this message