Re: PL/SQL performance question

response embedded . . .

On Thu, 13 May 2004 00:29:15 +0200, Marcel Stör <marcel at frightanic dot com> wrote:

>
>"Bricklen" <bricklen-rem_at_yahoo.comz> schrieb im Newsbeitrag
>news:97xoc.2984$j6.280_at_edtnps84...
>> Marcel Stör wrote:
>>
>> > Hi all,
>> >
>> > Just out of curiosity, I'd like to get your opinion on the following
>> > scenario:
>> > Lots of data (i.e. 2 million records) are periodically loaded into the
>db
>> > through SQL Loader. Unfortunately, each record needs to be tweaked
>before
>> > will eventually be saved. Would it be faster to have an on-insert
>trigger do
>> > this at record level or to have a procedure that will run once all
>records
>> > are stored in the table?
>> >
>> > Regards,
>> > Marcel
>> >
>> Without putting it to the test, I'd have to go option number 2. Triggers
>
>As you, I'm almost certain that the procedure approach will perform better.
>I'm just argueing with another DBA in our company...
>

So if it's just at the stage of 'animated discussion' between two DBA's, why not put it to the test and see which is faster? And see if the difference is siginificant enough to matter? <snip> Received on Thu May 13 2004 - 07:34:46 CDT