RE: Is there a performance advantage to using placeholders with Sybase?

OpenClient can do array binding, though I've never used it.

For execution of RPC (procs using placeholders) you must use the form 
"exec procname ...".

And lastly - if you are using FreeTDS then most of this (placeholders, 
array binding, RPC execution) doesn't work anyway, because FreeTDS's 
implementation of OpenClient isn't complete in this respect (or at least 
wasn't last time I looked - I have to admit that I don't really look all 
that often...)

Michael




"Ed Avis" <[email protected]> 
08.01.2008 11:48

To
<[email protected]>, <[email protected]>
cc

Subject
RE: Is there a performance advantage to using placeholders with Sybase?






Michael Peppler wrote:

>I haven't checked execute_array vs execute - off-hand I don't 
>think that there would be any real performance advantage. 

In some DBDs execute_array() is implemented to have just a few round trips 
to the database rather than one per row.  To get that with Sybase I 
imagine you must use bcp.

>For emulating placeholder behavior in more complex T-SQL code 
>- sure it could be done, but it would mean a lot more syntax 
>analysis in the prepare() code itself,

I think an explicit flag would be needed somehow because parsing other 
people's SQL is a pain.

Hmm, I did an experiment:

    my $sth = $dbh->prepare('my_stored_proc ?');
    $sth->execute('x');

No error was raised even though I connected with RaiseError and 
ShowErrorStatement.  I am using DBD::Sybase with freetds to connect to 
MSSQL.

-- 
Ed Avis <[email protected]> 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.