Up Prev Next
From: michael dot peppler at bnpparibas dot com
Subject: Re: DBD::Sybase question
Date: Apr 25 2006 6:07AM
You can interact with an ASE 15 server with a 12.5.1 client with no
particular problems. There may be some issues with the more esoteric
OpenClient functionality, but as DBD::Sybase doesn't use this it shouldn't
be a problem.
So the short answer is that you can keep your current environment and add
the ASE 15 server to the interfaces file.
Moving forward however you should consider upgrading the client and
DBD::Sybase, so to answer your other questions:
- DBD::Sybase 1.00 will not build with OCS 15 due to changes in the library
names (and maybe other problems as well - I have never tried it).
- A DBD::Sybase binary should only be used at run-time with the same OCS
version that was used to build it (note: EBF changes are OK without a
- To have multiple DBD::Sybase binaries with a single perl installation you
need to set the PERL5_LIB env. variable or use the "use lib" directive in
your scripts to point to the directory that holds the DBD::Sybase binary
that you want to use. It is certainly feasible, but you obviously need to
set something up so that these settings are automatic (i.e. you don't want
to have to edit your scripts to set the correct environment :-)
That being said I only have a 15.0 installation here, and use it to
interface with all sorts of Sybase servers (including an antique 4.9.2
server!) and I have yet to see any problems.
firstname.lastname@example.org - 24/04/2006 10:14
To: dbi-users, sybperl-l
Subject: DBD::Sybase question
We are conducting a proof of concept to upgrade Sybase ASE 12.5.1 and
OpenClient 12.5.1 to Sybase ASE 15.0 and SDK 15.0 on Solaris 2.8. Our
current environment details are as follows:
Perl 5.005 (5.0 patchlevel 5 subversion 3)
Sybase OC 12.5.1
Sybase ASE 12.5.1
We'd like to retain Sybase 12.5.1 and it's perl environment as described
above but create a new environment for Sybase 15.0.0 and have the following
questions (any feedback will be greatly appreciated):
- do we need an entirely separate perl, DBI and DBD installation for the
Sybase 15.0.0 side of things?
- do we need DBD::Sybase 1.07 for Sybase 15.0.0
- is there anyway we can use the same perl installation but point it to
either DBD::Sybase 1.00 or DBD::Sybase 1.07
Thanks & Regards,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Notice: This e-mail and any attachments are intended only for the
or company to which it is addressed and may contain information which is
privileged, confidential and prohibited from disclosure or unauthorized
use under applicable law. If you are not the intended recipient of this
e-mail, you are hereby notified that any use, dissemination or copying of
this e-mail or the information contained in this e-mail is strictly
prohibited by the sender.
Whilst we run anti-virus software on all internet e-mails we are not liable
for any loss or damage. The recipient is advised to run their own
If you have received this transmission in error, please return the material
received to the sender and delete all copies from your system. Thank you.
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.