I think he may have also meant that most ODBC drivers use string replacement
on the client side for parameterized querys and hence bind variables are not
used even if you think you are using them. So the cpu is busier on the
server also which is really bad!
Jim
"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
news:tqf1sn6qeta6f9_at_news.demon.nl...
>
> "Rayden" <durlecht_at_msu.edu> wrote in message
> news:9o7vth$1r67$1_at_msunews.cl.msu.edu...
> > Hello all,
> >
> > i was wondering if using an ODBC connection is more cpu-intensive then
> using
> > a native oracle driver or even jdbc driver..
> >
> >
> > thanks in advance,
> >
> >
> > timis
> >
> >
>
> ODBC runs on top of sqlnet (the native driver), so yes, by design ODBC
> *must* be more cpu-intensive.
>
> Regards,
>
> Sybrand Bakker, Senior Oracle DBA
>
>
>
Received on Tue Sep 18 2001 - 20:16:50 CDT
