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: Lee Wenzler <Lee dot Wenzler at Roanoke dot com>
Subject: RE: Sybperl to MS SQL Server help
Date: Jul 3 2002 12:51PM

Thanks Michael. That's what it took! Because my unix login has
environment variables set for Sybase 12, it was messing up the FreeTDS
stuff. After re-installing the DBD::Sybase with the env SYBASE set to
/usr/local/freetds and unsetting the OCS-12_0 envs it works fine.

Do you see any problems using connections to both Sybase 12 and MS SQL
living in the same program? I need to transfer some data back and forth.
Thanks,

Lee Wenzler
Publishing Systems Manager
The Roanoke Times
 

>-----Original Message-----
>From: Michael Peppler [mailto:mpeppler@peppler.org]
>Sent: Tuesday, July 02, 2002 5:10 PM
>To: SybPerl Discussion List
>Subject: RE: Sybperl to MS SQL Server help
>
>On Tue, 2002-07-02 at 13:45, Lee Wenzler wrote:
>> I built the DBD::Sybase and tried it. I can connect ok with a sybase
>> server, but when I put in the server name of the MS SQL server (with
the
>> interface file set to TLI TCP transport for the JOBS server name.
>>
>> $dbh = DBI->connect("dbi:Sybase:server=JOBS", $user, $password);
>>
>>
>> I get this error:
>>
>> DBI->connect(server=JOBS) failed: OpenClient message: LAYER = (5)
ORIGIN
>> = (3) SEVERITY = (5) NUMBER = (6)
>> Message String: ct_connect(): network packet layer: internal net
library
>> error: Net-Library operation terminated due to disconnect
>>  at ./jobs.pl line 761
>>
>>
>> I'm not sure how the FreeTDS gets pulled into all this.
>
>Well - you have to build DBD::Sybase with the FreeTDS libs (i.e. point
>the SYBASE env variable at the FreeTDS installation when you build, and
>when you run a script).
>
>Then you need to create an interfaces file entry in the "old" format
>(not tli):
>JOBS
>	query tcp ether hostname port
>
>This *should* work correctly.
>
>If you have a recent SP of MS-SQL 7 then the Sybase libs should work as
>well - but they won't work with MS-SQL 2000.
>
>Michael
>
>
>> >-----Original Message-----
>> >From: Michael Peppler [mailto:mpeppler@peppler.org]
>> >Sent: Tuesday, July 02, 2002 4:02 PM
>> >To: SybPerl Discussion List
>> >Subject: Re: Sybperl to MS SQL Server help
>> >
>> >On Tue, 2002-07-02 at 12:53, Lee Wenzler wrote:
>> >> Dang, this is way too hard. This all started when I tried to
connect
>> to
>> >> a MS SQL server using Sybperl. I can get the FreeTDS stuff to work
as
>> >> far as the make check passing the login & logout, & change db
tests,
>> but
>> >> I'm lost after that. After not getting that to work, I tried to
get
>> >> unixODBC drivers to work. I've gone thru all the FAQs and keep
>> getting
>> >> deeper and deeper into this hole. Am I making this more
complicated
>> than
>> >> it needs to be (please say yes)??
>> >
>> >I think so - though I'm no specialist on this.
>> >
>> >I suggest that you forget about ODBC. Instead try building
DBD::Sybase,
>> >and use that with FreeTDS. I believe that this works reasonably
well.
>> >
>> >Michael
>> >--
>> >Michael Peppler / mpeppler@peppler.org /
http://www.mbay.net/~mpeppler
>> >mpeppler@zetatools.com / ZetaTools, Inc / http://www.zetatools.com
>> >ZetaTools: Call perl functions as Sybase stored procedures!
>>
>--
>Michael Peppler / mpeppler@peppler.org / http://www.mbay.net/~mpeppler
>mpeppler@zetatools.com / ZetaTools, Inc / http://www.zetatools.com
>ZetaTools: Call perl functions as Sybase stored procedures!