Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "Chen, Meeilei" <Meeilei dot Chen at kcc dot com>
Subject: RE: Concurrent usage both Sybase and FreeTDS
Date: Jul 8 2005 7:07PM

I have the same project like yours, use Perl to access both SQL server
2000 and Sybase 12.5 on HP-UX.
I am totally new on FreeTDS and any help you can give would much
appreciated also.
Reading what you had below, I gathered that I would need to install
FreeTDS, DBD::Sybase, DBD::FreeTds, DBI::Sybase, DBI::FreeTDS.

Before I got into all our problems (yes, we have all kinds of problems
just to install FreeTDS and DBD::Sybase) I want to ask you if you DID
installed DBI::FreeTDS?
I went to and found the DBI::FreeTDS and under the "BUG"
section it said "This is an ugly hack". That just scared me. Is there
any trick to do this?

-----Original Message-----
From: []
On Behalf Of Yair Lenga
Sent: Thursday, July 07, 2005 6:12 AM
Subject: Concurrent usage both Sybase and FreeTDS


I have to a project that will move data between Microsoft SQL server 
(2003) and Sybase server. The only way to access the SQL server is with 
FreeTDS (I'm using 0.63), tested with SQSH. The Sybase servers must be 
used using Sybase clients libraries (company rule).

Does anyone has experience on how to work with both databasesin the same

perl program. I was hoping to duplicate "DBD::Sybase" into 
"DBD::FreeTDS" that will be linked against the FreeTDS libraries, and 
then I can use 'dbi::Sybase' to access the Sybase server, and 
'dbi::FreeTDS' to access the SQL server.

My major concern is how to keep the '' separate. I'm not sure if

this is possible, and if there is a problem here.

Any advice will be appreciated.

Yair Lenga

This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.