ODBC driver for sybase, linked server

by Steve Lon » Sat, 22 Jan 2000 04:00:00

I've got a legacy database (sybase on NT) thousands of miles away and I
need to access it (via ODBC) as a linked server from within SQL Server.
Where can I find an ODBC driver for sybase system 11, and what will I
need to define the DSN & linked server?

All I have so far is the ip address/port number of the Sybase server,
the database & server names, and a Sybase user id/password.

I'd be very grateful for your help.

Top

1. MS SQL Server Linked Server And Sybase ODBC Driver

Scenario:

Sybase SQL Server 11

MS SQL Server 2000
Service Pack 2
System DSN (Sybase System 11 ODBC Driver v. 3.01.00.00)
to Sybase server
Linked Server over the defined DSN using MSDASQL
(provider for ODBC data
sources)

A simple SELECT query in a ASP page, using the DSN in a
ADO connection,
works fine (so that I'm sure the DSN is OK). But when the
same query is
adapted for execution through the linked server (and im
sure the query is
correct) over a MS SQL Server connection, I got the
following error
message:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: Unspecified error]
[OLE/DB provider returned message: [INTERSOLV][ODBC SQL
Server driver][SQL
Server]ct_bind(): user api layer: external error: This
routine cannot be
called when the command structure is idle.]

In Enterprise Manager, I can see all the Sybase schema
information normally
by clicking in the linked server.

Any comments ??

Thanks in advance

2. SQL Server 10 & logical volumes on AIX 4.1.4

3. link server on sql server using ole db provider for odbc driver

4. Universe file triggers, ODBC, and third party applications

5. Need ODBC Driver to link Sybase 10 from MS-Access 7.0

6. Need to get Servers in Network Neighborhood

7. Linked Server with 3rd party ODBC driver

8. Jr level Delphi Opportunities in San Francisco Area (south bay) don't miss out!!

9. Access Link To SQL Server 7 - ODBC driver

10. [ODBC Sql Server Driver]Communication link failure