August 25, 2005 at 8:48 am
I'm configuring a Sybase server as a linked server in an instance of SQL Server 2005 June CTP (Build 9.0.1187). I'm trying to decide whether to use the "Microsoft OLE DB Simple Provider", the "SQLXMLOLEDB" provider or the "SQLXMLOLEDB 4.0" provider. Has anyone else tried connecting a 2005 instance to Sybase? If so, what are the benefits and drawbacks of using these providers?
“If you're not outraged at the media, you haven't been paying attention.”
August 26, 2005 at 3:50 am
No experience on 2005 but we have several Sybase Linked Servers on our SQL Server 2000 boxes. No XML Options but we can't get the 'Simple Provider' to work.
Instead we use the OLE DB Provider for ODBC, specifying an ODBC DSN plus the Sybase login & password. The DSN references an entry in a piece of Sybase middleware called DSEDIT which points to the IP address & port number of the Sybase Server.
We have to install the Sybase Client on our Windows Servers for DSEDIT and the Sybase ODBC drivers. Basically it's very fiddly and involves several components (Linked Server/ ODBC DSN/ DSEDIT) plus the co-operation of our Sybase DBAs which isn't always forthcoming.
August 26, 2005 at 6:17 am
Well at least I don't have the Sybase DBA issue. My boss IS the Sybase DBA and he asked me to do this.
For now, I'll try the Simple provider. Of course, a lot will depend on the exact query he wants me to run. I'll make it a point to pose updates to this posting as I work through the process.
“If you're not outraged at the media, you haven't been paying attention.”
November 11, 2005 at 1:50 am
Hi Peter
Could you pls help me with this type off linked server?
I'm battling to get the sql script correct to create the linked server to Sybase.
November 14, 2005 at 3:22 pm
I have not used Sybase ASA as a linked server; but I have used it as a data source. I was lucky in that ASA was not available when I needed it, so I got a copy and installed it - so when I went to connect to the "real" instance I had the native drivers from the local installation. We discovered that you could not connect if the ASA was on a different subnet. This was true of Sybase Central to ASA as well; but fixable for the Sybase tools. You need to add the "commlinks=tcpip" command syntax in the connect string to connect across subnets. There was no place within Integration Services (in Visual Studio) to edit this syntax into the connect string. We ended up using Sybase Direct Connect and replicating straight into SQL Server. Hope this helps.
November 14, 2005 at 3:23 pm
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply