Re: Stored Procedure/Trigger Performance question

From: Van Messner <vmessner_at_bestweb.net>
Date: Sat, 19 May 2001 04:13:35 GMT
Message-ID: <PpmN6.2140$gA.734701_at_monger.newsread.com>


You'll have to try each approach and do some load testing to find out. With Oracle 8i you can use a multi-table view and an "instead-of" trigger on the view to insert rows into all the relevant base tables. The SQL Server rules don't necessarily apply to Oracle.

Van

"Scott Pawluk" <spawluk_at_nospam.city.winnipeg.mb.ca> wrote in message news:SLRL6.982$U61.16728_at_news2.mts.net...
> Here is my scenario:
>
> We are a small shop using Oracle 8i for development. We don't have anyone
> with professional DBA training and so our most senior programmer has taken
> this role. She is currently trying to setup triggers so that we can send
 an
> INSERT to a query with multiple tables and the trigger will handle all the
> proper INSERTs. She feels this is the best way for security purposes.
>
> Now I've done some DBA work on MS-SQL Server before (not certified
 however)
> and from the System Administration course that I took for SQL Server 6.5,
 I
> was told that Stored Procedures are the best way to handle inserting data
> into multiple tables on a regular basis. I'm still new to Oracle so I
 don't
> want to step on any toes unless I have to.
>
> My question is, which is faster? A single stored procedure to update the
> data, or a series of triggers? I have also been told that there are
> limitations to what triggers can access. Is this true as well?
>
> Thank you,
>
> Scott Pawluk
> Programmer/Analyst
> City of Winnipeg
>
>
> PS-To reply directly, remove the nospam from my email address.
>
>
Received on Sat May 19 2001 - 06:13:35 CEST

Original text of this message