Sybase Adaptive Server is a relational database management system. The application runs on both on Windows platforms and on most Unix systems. You must have Sybase Adaptive Server 12.x or 15.x client installed to connect to Sybase Adaptive Server databases. With this connector, Map Editor can read and write to Sybase Adaptive Server tables.

Use of the Sybase DSEdit utility to set up the Sybase server is recommended.

We recommend that you use the Sybase DSEdit utility to set up the Sybase server.

If you try to make a live connection to a database to which you do not have direct access, the integration platform displays a message indicating that the connection is simulated. In simulated mode, it may not be possible to view all property options. To view all property options, install and configure the database client before connecting on the integration platform.

Perform the following Sybase settings:

This connector sets field width in bytes. The variation is the number of characters that can be included into a given field. For additional details, see Database Connections.

Unless there is a unique index in the table that is being updated or deleted, the Update and Delete output modes do not function properly with this connector. You must have a unique index field to make a comparison with an existing record. If the index field matches an existing record, then the record can either be updated or deleted. If the index field is not unique, Map Editor cannot determine which record needs to be updated or deleted. You can have more than one index field, but there must be a unique index field for Update/Delete modes to work.

Map Editor can read accurate data types on existing tables and views in Sybase Adaptive Server, but not from SQL statements. Consequently, if you are connecting with a SQL statement, the data types that show in Map Editor are either synonyms or generic versions of the data types used in the database schema. This applies especially to user-defined data types.

Connector parts are the fields you configure to connect with a data source or target.

The settings that are available depend on the connector you select.

For a list of all parts for source connectors, see Specifying Connector, Parts, and Properties.

For a list of all parts for target connectors, see Specifying Connector, Parts, and Properties.

You can specify the following source (S) and target (T) properties:

The packet size is automatically set using the following algorithm:

To determine how large to set the packet size, you can first set PacketSize to 0 (auto) and establish a connection. Then open the log file to get the actual size of the packet, and use that value in the PacketSize property setting.

The advantage of the auto default setting is that a connection can accept a large packet size. The disadvantage is that Sybase may log an error if the connection fails.

Sybase documentation describes PacketSize as follows:

"Increase the packet size for the connection: On most platforms, the packet size default is 512 bytes. This default is provided for backward compatibility. Larger packet sizes, 2048 to 4096 bytes, for example, almost always yield better performance. This is generally true for applications that fetch rows with large columns, rows with lots of columns, or lots of rows with a few small columns. It is especially true for applications that do bulk copy data transfers or that handle text and image data.

To increase a connection's packet size, set the CS_PACKETSIZE connection property, via ct_con_props, prior to opening the connection."

Constraint DDL is similar to the support provided for SQL pass-through with the SQL import connectors. Each line must be a valid ODBC DDL statement.

For example, consider the following statements, which would create two indexes on the table mytable:

The first index does not allow duplicates and the index values are stored in ascending order. The second index is a compound index on Field2 and Field3.

ConstraintDDL is executed only if the replace mode is used for the target. If there are any errors, they are written to the error and event log file. During transformation, the transformation error dialog box shows the errors. If desired, you can ignore the DDL errors and continue the transformation.

ConstraintDDL also supports an escape mechanism that allows users to specify DDL in the native SQL of the database system. Any statement that is preceded by an "@" is sent directly to the database system.

Consider the following statement, which is an Access DDL statement for creating a primary key for the table mytable:

The Access ODBC driver does not support the SQL extensions needed to create a primary key with the ODBC variant of the SQL CREATE statement. The only way you can create the primary key for an Access table is with the native SQL.