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

You can use placeholders with a stored proc execution. This will tell 
DBD::Sybase to execute an RPC call rather than a SQL Language call to 
execute the proc. This is slightly faster (no SQL parse), but because 
DBD::Sybase does not know the type of all the parameters (it could look it 
up, but that's also an overhead) you have to specify the datatype of the 
parameters when you bind.

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

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, to determine if the SQL buffer is a single command 
or not, and triggering the native placeholder handling vs. emulation 
depending on the situation.

Michael





"Ed Avis" <[email protected]> 
08.01.2008 10:59

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

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






Michael Peppler wrote:

>Yes, OpenClient has an API that creates a "prepared" statement 
>(actually known as a light-weight stored procedure) for you, 

Suppose the query you want to prepare is itself to run a stored procedure.

    exec my_proc ?, ?, ?

Is there any performance advantage to using a prepared statement here?

With DBD::Sybase, does execute_array() have any performance advantage over 
calling execute() repeatedly?

>Another limitation is that placeholders can only be used for 
>single statement SQL batches (i.e. a single 
>SELECT/INSERT/UPDATE/DELETE statement). You can't use 
>placeholders if you want to submit a statement that includes 
>other T-SQL code (flow control, conditionals, while loops, etc). 

Hmm, couldn't DBD::Sybase work around this with a 'fake placeholders' 
feature?  I think some other DBDs have that because their DBMSes don't 
support placeholders at all.

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