Every database has its own dialect of SQL. ASE uses a dialect of SQL called Transact-SQL® (T-SQL). Both IBM and Sybase ASE SQL syntaxes support the ANSI SQL-1 standard. As a result, applications written for specific tables are relatively portable between ASE and DB2 UDB. However, the DB2 access service does not support all SQL statements. If unsupported extensions exist in a SQL statement, the DB2 access service passes the SQL statement to the target, which may accept it or return a syntax error.
To make the various dialects look like common SQL, the DB2 access service supports two transformation modes, called sybase and passthrough. For more detail, see the section called “Description of passthrough and sybase transformation modes”.
Although the transformation mode primarily affects the way the DB2 access service treats incoming SQL statements, it also affects these functional areas:
Transaction management
Datatype handling
set statements
Global variable processing
DB2 stored procedures
Catalog stored procedures (CSPs)
System stored procedures
Remote stored procedures (RSPs)
Host-resident requests
Interoperability with:
ASE/CIS
ODBC driver
Replication Server
When you configure the DB2 access service with a specific transformation mode, that mode is effective for all client connections, unless you use a set statement to alter it for a specific connection.
Using the SQLTransformation property, you can specify how the DB2 access service processes SQL syntax.
The DB2 access service never transforms these SQL statements:
set statements
select @@global variable statements
transfer statements
CSP requests
Instead, the DB2 access service processes these statements and takes any corresponding action needed.
