This is a cross-post from Stack Overflow, and someone there clued me in to your beta, so I figured I'd ask the experts. Thanks for your help.
I have a Sybase ASE server that I'm able to connect to with ASE iSql totally fine. The database definition in my sql.ini file looks like:
to connect with iSql, I can make the following command-line call and it works:
My ultimate goal is to use SQL Anywhere's ADO.Net Entity Framework connectivity for a RIA service I'm writing. I'm trying to connect now using SQL Anywhere through Sybase Central (rather than through Visual Studio), and can't get it to work. Under the Identification tab, I use and for my credentials and leave the bottom half as "None", under the Database tab, I specify for the Server name, and under Network I check "TCP/IP", and specify as the Host, and as the Port. I get the following error:
I'm sorry in advance if I left out significant details. I'm new to Sybase, having a strictly Oracle background. If I left out anything you need to know, please post a comment and I'll update the question. Thanks for helping a Sybase newb.
asked 20 Nov '09, 20:03
Let's start with a couple questions:
The SQL Anywhere ADO.Net driver can be used to connect to a SQL Anywhere Server, and not to ASE.
A possible architecture to ultimately retrieve data from ASE would be to use SQL Anywhere's Remote Data feature. (http://dcx.sybase.com/index.html#1101en/dbusage_en11/ug-accessrd.html)
Using this approach, your RIA application would use SQL Anywhere's ADO.NET interface to connect to a SQL Anywhere server. Inside the SQL Anywhere database, you have defined proxy tables to read data from your ASE server.
There are obvious trade offs with this approach, such as performance. You would also have to ensure that any data updates you want to enable work as expected.
Some might wonder why you are using the ASE. Depending on your exact circumstances, a SQL Anywhere Server might satisfy all your requirements.
answered 20 Nov '09, 22:38