Re: External Procedure or Java Stored Procedure

FYI in preliminary testing of "external procedures" (written in C) with Oracle 8.0.6.0.0 (32-bit) on HP-UX 11.0, the memory used by a session increased over 10MB. this was 10MB memory for each session that made a call to the external procedure. yikes!

things may have changed with 8i (and 9i)... the biggest change being, of course, the introduction of java.

"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:3bf03305$0$1775$afc38c87_at_news.optusnet.com.au...
> Don't necessarily rely on this until you et confirmation from someone
else,
> but a new feature of 9i is the ability to have external procedures called
> via dedicated agents. Until 9i, all external procedure calls were handled
> solely by the one agent, EXTPROC. That's not a very scalable solution,
and
> it's not very robust either (one dodgy external routine can bring down
> EXTPROC, and thus bring down all others).
>
> For that reason alone, I would have thought Java Stored Procedures were
the
> way to go.
>
> <sits back and awaits the contradictions! :-)>
> Regards
> HJR
> --
> Resources for Oracle: http://www.hjrdba.com
> ===============================
>
>
> "Steve Johnson" <johnst_at_ncs.com> wrote in message
> news:3BF012BC.D56998CA_at_ncs.com...
> > I have a program written in either (C++ or Java) which I need to call
> > from an Oracle Stored Procedure.
> >
> > Is it more efficient to call the program as an external procedure (C++)
> > or put the Java into the database and call a Java Stored Procedure?
> > This program will get called very frequently, possibly thousands of
> > times a day. I'm using Oracle 8.1.6.3 and HP 11.
> >
> > What are the Pro's and Con's?
> >
> > Any help would be appreciated.
> >
> > Thanks...
> >
>
>
Received on Mon Nov 12 2001 - 16:25:08 CST