cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Linked Sybase from SQL Server

0 Likes
5,395

How do I create (step by step) one sybase linked server to SQL Server In ODBC not appear Ole Provider driver for creation of Alias I do not know where to start. :( I am using Sybase ASA 9 and SQL Server 2012

View Entire Topic
Former Member
0 Likes

ASA 9 is past support for a number of years now and has never been tested for use with a current release of SQL Server. but the concepts are nothing new.

You will want to review proxy tables and remote servers. Do review the version 9 doc set that comes with the product but the equivalent section from 10.0.1 is viewable online

http://dcx.sap.com/index.html#1001/en/dbugen10/ug-proxy-omni-using.html

Another alternative is to reverse that connection. Version 9 has an OLE/DB driver and I believe others have used that to make a remote data access for SQL Server to ASA (though that combination has had no official testing either, of course).

best of luck

VolkerBarth
Contributor
0 Likes

I believe others have used

I guess most of these (including me) have experienced that it's faaaaaar easier to access data in SQL Anywhere from a remote MS SQL Server (aka remote data access/proxy tables) than the opposite (using MS SQL server's Linked server feature). If you need to do the later, here are some of those FAQs on that topic:

http://sqlanywhere-forum.sap.com/search/?q=linked+server+ms+sql&Submit=search&t=question

That's not to say remote data access would not have its obstacles, either:)

Former Member
0 Likes

Thanks Volker. We try to be helpful that way.

I suggested the other approach, only because, sometimes it makes more sense to use the technology that matches the data movement requirements or one that allows processing (SQL executing, views, permissions, ... ) at the desired point of control; even if that means using that "other" technology.

Caveat Given the untested combination of product versions involved, you may find one approach a little more stable than the other. Testing for stability is highly recommended because of post-maintenance level of support available for SQL Anywhere 9. Of course, that observation does justify upgrading to current releases more than it does the picking the lesser of 2 evils. {pls. no Master & Commander references}

VolkerBarth
Contributor
0 Likes

Nick, I surely agree that's most important to choose the approach that fits the requirement, so if Walmir has to use data within ASA 9 from a remote MS SQL Server ASA's remote data access will be the way to go whereas when he needs to use ASA9 data within a MS SQL Server environment, MS SQL Server's Linked Server feature will be more appropriate. I am not sure what he is about to do.

I just wanted to mention that me (and others like Breck, AFAIK) who had to use both approaches usually have felt that ASA's remote data access feature is much easier to use.

Breck_Carter
Participant
0 Likes

...easier, faster, safer, better in every imaginable way 🙂