Before you can map remote objects to a local proxy table, you must define the remote server where the remote object is located. When you define a remote server, the server's class must be chosen.
A server class specifies the access method used to interact with the remote server. Different types of remote servers require different access methods. The server class provides SQL Anywhere detailed server capability information. SQL Anywhere adjusts its interaction with the remote server based on those capabilities.
The server classes are:
SAODBC for SQL Anywhere.
ULODBC for UltraLite.
You cannot create a remote server for an UltraLite database running on Mac OS X.
ADSODBC for Advantage Database Server.
ASEODBC for Sybase Adaptive Server Enterprise (version 10 and later).
DB2ODBC for IBM DB2.
HANAODBC for SAP HANA.
IQODBC for SAP Sybase IQ.
MSACCESSODBC for Microsoft Access.
MSSODBC for Microsoft SQL Server.
MYSQLODBC for Oracle MySQL.
ODBC for all other ODBC data sources.
ORAODBC for Oracle Database servers (version 8.0 and later).
When using remote data access, if you use an ODBC driver that does not support Unicode, then character set conversion is not performed on data coming from that ODBC driver.
When you define a remote server, an entry is added to the ISYSSERVER system table for the remote server.
Creating remote servers (SQL)
Creating remote servers (Sybase Central)
Dropping remote servers (SQL)
Dropping remote servers (Sybase Central)
Altering remote servers (SQL)
Altering remote servers (Sybase Central)
Listing the tables on a remote server (SQL)
Remote server capabilities
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|