Re: PL/SQL performance question

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

> are generally slow. Also, it depends how complicated your "tweaking" is.
> The more complicated it gets, the more useful pl/sql gets.

So? Bother triggers and procedures use PL/SQL ;-)

Regards,
Marcel Received on Wed May 12 2004 - 17:29:15 CDT