PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: todd dot e dot rinaldo at jpmorgan dot com
Subject: RE: Is there a performance advantage to using placeholders with Sybase?
Date: Jan 7 2008 11:15PM

I would say yes. Sybase has to prepare the query (compile) every time you
run a prepare. If you only 1 run prepare, then you're having to deal with
query time only. This should be more efficient. I've been told there's a
risk of some sort of funky tempdb usage based on the contents of the
prepare when place holders are involved, but I've really never noticed an
issue. 

 

P.S. If you're looking to optimize, then another thing you should look at
is prepare_cached.

 

  _____  

From: owner-sybperl-l@peppler.org [mailto:owner-sybperl-l@peppler.org] On
Behalf Of Wechsler, Steven
Sent: Monday, January 07, 2008 4:25 PM
To: sybperl-l@peppler.org
Subject: Is there a performance advantage to using placeholders with
Sybase?

 

DBI documentation says that you're better off using placeholders rather
than continully preparing and executing, or using $dbh->do(). Does this
hold true with Sybase?

 

Steve Wechsler | steven.wechsler@mtvstaff.com 
Sybase/SQL Server/MySQL Database Administrator 
212-846-5683 

MTV Networks 

 



Generally, this communication is for informational purposes only
and 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. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  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.