User Guide : Map Connectors : Source and Target Map Connectors : Sybase Adaptive Server 12.x and 15.x
Share this page             
Sybase Adaptive Server 12.x and 15.x
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.
Note:   you install the Sybase client on a DataConnect system, check that the path environment variable has both the default installation directory and the Sybase directory. For a 64-bit Sybase 15 client installation, also verify that the path contains C:\Sybase_Client\OCS-15_0\lib.
Connector-Specific Notes
Setting up the Sybase Server
We recommend that you use the Sybase DSEdit utility to set up the Sybase server.
Note:  When you install the Sybase client on your integration platform system, check that the path environment variable has both the default installation directory and the Sybase directory. For a 64-bit Sybase 15 client installation, also verify that the path contains C:\Sybase_Client\OCS-15_0\lib
Simulated Database Connections
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.
Sybase Settings
Perform the following Sybase settings:
In Windows, set the environmental variable LC_ALL or LANG to a valid locale defined in Sybase_Install_Directory\locales\locales.dat file. It is recommended to add Set.LC_ALL=default to file.
In Linux:
1. Set the environmental variable SYBASE=Sybase_Install_Directory. It is recommended to add Set.SYBASE=Sybase_Install_Directory to file.
2. Add Sybase library to file: /lib:Sybase_Install_Directory/OCS-15_0/lib3p64:Sybase_Install_Directory/OCS-15_0/lib3pRename based on the order.
Field Width
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.
Update/Delete Modes
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.
Note:  Map Editor now supports SQL stored procedures in Sybase Adaptive Server.
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.
Property Options
You can set the following source (S) and target (T) properties.
12x, 15.x
Type of encoding to use for reading and writing data. The default is ANSI, which is the standard in the US.
12x, 15.x
Allows you to control how often data is committed to the database when the AutoCommit property is set to False.
The default value is zero that is, the data is committed at the end of the transformation, allowing rollback on error. This is the slowest setting. When performing large transformations, this is not practical as it may produce too many transaction log entries.
Specifying a nonzero value indicates that data is committed to the database after inserting or updating specified number of records.
12x, 15.x
Pass-through mechanism for setting additional data definition language (DDL) statements to be executed when a new table is created. DDL is used to define keys, indexes, constraints, and integrity rules for SQL databases. There is no default. For more information, see ConstraintDDL.
12x, 15.x
Enables insertion of user-defined identity values in identity fields. Default is false.
12x, 15.x
When set to True, enables viewing of all tables created by the DBA. Default is false.
Only applicable if you are logged onto the database as the database administrator. Only the database administrator has access to SystemTables.
12x, 15.x
If set to True, this property allows you to see the view names in the table list along with the table names. Default is True.
Note:  This property supports only Append and DeleteAndAppend output modes and does not support the Replace output mode.
12x, 15.x
Provides a pass-through mechanism for SQL connectors where advanced users can construct the Where clause of the SQL query themselves. It can be used as an alternative to writing a lengthy query statement. You may use this to instruct the SQL database server to filter the data based on a particular condition before sending it to the integration platform. There is no default value for this property.
Note:  This property is not applicable when the source connection is a query statement or file. This property enables data filtering when you select a table.
The packet size is automatically set using the following algorithm:
The initial packet size is 16384 (32 * 512) bytes.
If the connection fails, the outcome depends upon the size, as follows:
If size > 1024, the packet reduces to one-quarter the size until the connection succeeds.
If size <= 1024, the packet reduces to one-half the size until the connection succeeds.
When the connection succeeds, the value of PacketSize is logged.
Working with Large Packet Sizes
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:
CREATE UNIQUE INDEX index1 ON mytable (Field1 ASC)
CREATE INDEX index2 ON mytable (Field2, Field3)
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:
@CREATE INDEX pk_mytable ON mytable (Field1, Field2) WITH PRIMARY
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.
Note:  This option works only in Replace mode.