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: "Pantera, Joseph F dot " <JPantera at gibsondunn dot com>
Subject: RE: Using isql-type Unix tool to connect to MSSQL2000...
Date: Jun 30 2003 5:28PM

Thank you Michael.  Is there something similar to replace a straight "bcp" (out of ksh...)?  My programmers here pointed out they need that type of functionality too (only isql and bcp).

- Joe Pantera

-----Original Message-----
From: Michael Peppler []
Sent: Saturday, June 28, 2003 10:53 PM
To: Pantera, Joseph F.
Cc: Sybperl-L Mailing List
Subject: Re: Using isql-type Unix tool to connect to MSSQL2000...

On Sat, 2003-06-28 at 02:59, Pantera, Joseph F. wrote:
> Michael / Sybperl List-Serve:
>     I know this is not a Sybperl question, but I think the people who
> normally get involved here might be able to provide some insight on
> this...  Have some rather old Unix korn shell scripts that do data
> extraction (isql), insertion (bcp) from other Sybase databases.  Those
> databases are about to be converted to MSSQL2000.  Does anyone know of
> a way to make Sybase isql (or perhaps a third party tool that works
> "just like" Sybase isql) work with MSSQL2000?  I have many perl
> scripts that I'm converting to do this type of thing, but the scripts
> I'm talking about using here are in another support group's domain,
> and they really don't want to touch them at this time...

Install FreeTDS ( and then build sqsh
( That'll give you something that is very close to

Michael Peppler                              Data Migrations, Inc.       
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or 
long term contract positions -


This message may contain confidential and privileged information.  If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete this message.