![]() ![]() ![]() For each version of SQL Anywhere, SAP publishes a list of supported versions for each of these key components. SAP identifies supported Linux installations for SQL Anywhere based on the version number of the following key components of the operating system: the kernel, glibc, ncurses, kerberos and LDAP libraries. This multitude of possible Linux installations poses a challenge for companies, such as SAP, that want to maintain an open and flexible approach to supporting Linux, yet require a practical means of identifying which Linux installations they support. As a result, a wide variety of Linux installations are possible. In addition, many installation options are available, meaning that not all portions of the operating system may be installed, or all parts of any given installation may not be of the same vintage. Unlike other common operating systems, the Linux operating system is available from several vendors. The SQL Anywhere approach to Linux platform support What can the correct connection string be for an asaconnection? isn't any help.The SQL Anywhere approach to Linux platform support Support philosophy Exceptions Future Linux releases Key components Tested Linux distributions The Sybase Central 9 app does not work in windows 7 nor windows 10, so we couldn't generate a connection string that way. Once we added the reference and changed all the code to ASA objects instead of SA objects, we tried opening the connection and the connection string couldn't be parsed. Since all drivers from 12 to 17 trigger the chained option, we went back to the version 9 driver, which you have to manually add a reference to the dll to. If this fails we will have to change the way the code is retrieving the data so as to not trigger the timeout. We are trying to connect because via ODBC a simple query times out, so we want to try changing the driver (using SA objects instead of ODBC objects). No one knows how to upgrade the database or the server. I don't know if the database does not support it or the server is the one that doesn't. It keeps doing it even in version 17, and I don't know how to stop it from doing that on this connection to this database. From version 5 to version 12 something changed, and when trying to open an ADO.NET connection, it tries to execute a CHAINED=on parameter after opening. SQL Anywhere used to come bundled with Sybase Powerbuilder, and now is the property of SAP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |