ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

white papeR
ASE ODBC Driver and OLE DB
Provider Migration Technical
Whitepaper
www.sybase.com

taBLe Of cOntents
1 Introduction
1 ODBC Architecture
2 Overview of OLE DB
2 Migration Overview
3 Supported Platforms
3 Sybase Driver Names
3 Migration Tools Simplify the Migration Task
4 Sybase ASE Data Source Administrator
4 The DSNMigrate utility
4 Properties not Migrated
6 Automatic Data Source Backups
6 How to Migrate for Large Number of Clients
6 Developing New Applications Using Sybase ODBC and OLE DB Providers
6 Testing Considerations
6 Connection Property Matrix
8 Sybase ASE Data Source Administrator
18 Uninstalling OEM Products
22 References
x

1 intROductiOn
The ODBC driver interface is a call-based application programming interface defined by Microsoft Corporation as
a standard interface for database management systems. OLE DB provider is a data access model also developed by
Microsoft. It uses the Component Object Model (COM) interface and, unlike ODBC, does not need to assure that the
data source uses an SQL query processor. In previous releases of Adaptive Server Enterprise (ASE), Sybase shipped third-
party ODBC driver and OLE DB provider interfaces for users to connect to Adaptive Server Enterprise for data access.
Now Sybase has developed its own ODBC driver and OLE DB provider interface products to provide our customers with
better support for database connectivity.
The new Sybase drivers provide many benefits to our customers.
1. Customer requirements are incorporated in product design and development: Since these drivers are developed in
house, Sybase can incorporate customer requirements in product design and development.
2. Frequent updates of feature enhancements and bug fixes will be available directly from Sybase.
3. Full Support for ASE 15.0 features: These drivers support all ASE 15.0 features and are engineered to work
seamlessly with ASE.
This document provides guidance to developers who are migrating a third-party ODBC driver or OLE DB provider
to Sybase’s ODBC driver or OLE DB provider. It describes the appropriate migration tools you can use to facilitate the
work, and it also lists various steps necessary to complete your migration. Furthermore, it provides an effective way for
large enterprises to migrate datasources on multiple machines.
2 OdBc aRchitectuRe
The ODBC architecture has four components:
• Application. Performs processing and calls ODBC functions to submit SQL statements and retrieve results.
• Driver Manager. Loads and unloads drivers on behalf of an application. Processes ODBC function calls or passes
them to a driver.
• Driver. Processes ODBC function calls, submits SQL requests to a specific data source, and returns results to the
application. If necessary, the driver modifies an application’s request so that the request conforms to syntax
supported by the associated DBMS.
• Data source. Consists of the data the user wishes to access and its associated operating system, DBMS, and
network platform (if any) used to access the DBMS.
The following illustration shows the relationship between these four components.
1

2
Please note the following about this diagram: First, multiple drivers and data sources can exist, which allows the
application to access data from more than one data source simultaneously. Second, the ODBC API is used in two
places: Between the application and the Driver Manager, and between the Driver Manager and each driver. The
interface between the Driver Manager and the drivers is sometimes referred to as the service provider interface, or SPI.
For ODBC, the application programming interface (API) and the service provider interface (SPI) are the same; that is,
the Driver Manager and each driver have the same interface to the same functions.
3 OveRview Of OLe dB
Today, a vast amount of the critical information necessary for conducting day-to-day business is found outside of
traditional, corporate production databases. Instead, this information is found in file systems, in indexed-sequential
files such as Btrieve, and in personal databases such as Microsoft® Access and Microsoft Visual FoxPro®; it’s also found
in productivity tools such as spreadsheets, project management planners, and electronic mail; finally, more and more
frequently, it’s found on the World Wide Web.
To take advantage of the benefits of database technology, such as declarative queries, transactions, and security,
businesses have traditionally had to move the data from its original containing system into some type of database
management system (DBMS). This process is expensive and redundant. Furthermore, businesses need to be able to
exploit the advantages of database technology not only when accessing data within a DBMS but also when accessing
data from any other type of information container. To address this need, Microsoft created OLE DB.
OLE DB is a set of Component Object Model (COM) interfaces that provide applications with uniform access to data
stored in diverse information sources and that also provide the ability to implement additional database services.
These interfaces support the amount of DBMS functionality appropriate to the data store, enabling it to share its data.
4 MigRatiOn OveRview
To migrate your applications from the third-party ODBC driver and OLE DB provider to Sybase’s ODBC driver and
OLE DB provider, it is important to understand the structure of your environment. The following diagram illustrates an
ODBC application that connects to Adaptive Server Enterprise. At the core of the ODBC application is the ODBC driver,
which facilitates connectivity to ASE.
To migrate from a third-party ODBC driver to the Sybase ODBC driver,
1. Replace the third-party driver with the Sybase ODBC driver.
2. Change the data source definitions (DSN) using the migration tool.
Your application should function with no additional changes.
To migrate from a third-party OLE DB provider to the Sybase OLE DB provider,
1. Replace it with the Sybase OLE DB provider.
2. Use the migration tool to transform existing third party data sources to the Sybase OLE DB provider format.
Your application should function with no additional changes.

5 suppORted pLatfORMs
The ASE OLE DB Provider is designed to work with OLE DB 2.5 and later. Supported platforms include Microsoft
Windows NT 4.0, 2000, XP, 2003, Vista and 2008 (x86 and x64 architectures).
The ASE ODBC Driver supports all Level 2 features. The driver is supported on Windows 2000, 2003, XP, Vista and
2008; 32-bit and 64-bit (x86 and x64 architectures); Linux 32-bit and 64-bit (x86 and x64 architectures), and Mac OS X.
See the ASE Software Developer’s Kit and Open Server 12.5.1 Installation Guide for version details regarding
supported platforms.
6 syBase dRiveR naMes
Upon installation, the driver DLLs are copied to their respective install directories. Listed below are the important
attributes for filename, driver name and product name:
Sybase:
OEM:
%SYBASE%\DataAccess\[ODBC|OLEDB]\dll
ODBC filename: sybdrvodb.dll [winx64: sybdrvodb64.dll]
ODBC driver name: Adaptive Server Enterprise
ODBC product name: ASE ODBC Driver by Sybase
OLE DB filename: sybdrvoledb.dll
OLE DB provider name: ASEOLEDB or “Sybase OLEDB Provider”
OLE DB product name: ASE OLEDB Provider by Sybase
%SYBASE%\[ODBC|OLEDB]
ODBC filename: syodase.dll
ODBC driver name: Sybase ASE ODBC Driver
ODBC product name: “Sybase ASE ODBC Driver “
or “ODBC Driver Kit”
OLE DB filename: sydaase.dll
OLE DB provider name: Sybase.ASEOLEDBProvider
or “Sybase ASE OLE DB Provider”
OLE DB product name: Sybase ASE OLE DB Provider
7 MigRatiOn tOOLs siMpLify the MigRatiOn task
One of the critical issues encountered when migrating from the OEM ODBC and OLE DB drivers to the Sybase
organic drivers is one of migrating existing data sources.
In addition, with OLE DB the OEM driver supports the creation of external data sources; but, there is no standard
tool that can be used for all drivers. Thus, for ODBC, the ODBC Administrator must deal with all of these issues.
The Sybase ASE Data Source Administrator addresses both of these problems. It displays a list of existing data
sources for both of the drivers (OEM and Sybase and ODBC and OLE DB). It also allows the creation and manipulation
of Sybase OLE DB data sources, as well as the migration of existing OEM data sources to Sybase organic data sources.
Lastly, Sybase provides a command line utility for migrating data sources in DOS batch procedures; this is ideal for
mass-migrating data sources while the Data Source Administrator provides an interactive environment for migrating
fewer or individual data sources. Go to section 17 for more details about these tools.
3

4
8 syBase ase data sOuRce adMinistRatOR
The Data Source Administrator is designed to provide users with an interactive tool to enable the migration of
both OEM ODBC and OLE DB data sources, as well as creating and modifying Sybase OLE DB data sources. All ODBC
data sources are maintained using the ODBC Data Source Administrator available with the Microsoft Windows
operating system.
To run the Data Source Administrator, click the ‘Data Source Administrator’ menu item in the ‘DataAccess’ program
group under ‘Sybase’, or run ‘sybdrvadm.exe’ from the install directory at ‘%SYBASE%\DataAccess\bin’.
Upon startup, the tool displays all OLE DB and ODBC data sources for both OEM and Sybase. Users can choose the
OEM data source to migrate, or alternatively create, modify or delete existing Sybase OLE DB data sources.
9 the dsnMigRate utiLity
This command line utility provides users with the same capabilities as the interactive Data Source Administrator
described above, but being a non-UI tool, it provides users with a command that can be used in DOS batch procedures
to help automate the migration process.
To run the command line utility, run ‘dsnmigrate.exe’ which is also located in the install directory at ‘%SYBASE%\
DataAccess\bin’. Running this utility with the ‘/h’ argument displays all the available migration options listed below;
you may choose the option which best suits your environment.
/?, /h, /help Displays this message. This message will also be displayed if dsnmigrate.exe is called with no
command line arguments.
/oledb Puts dsnmigrate into OLEDB-mode. By default ODBC DSNs are migrated.
/l Displays a list of all Sybase OEM User and System DSNs
/ul Displays a list of all Sybase OEM User DSNs
/sl Displays a list of all Sybase OEM System DSNs
/a Converts all Sybase OEM User and System DSNs
/ua Converts all Sybase OEM User DSNs
/sa Converts all Sybase OEM System DSNs
/dsn Converts specific Sybase OEM User or System DSN
/udsn Converts specific Sybase OEM User DSN
/sdsn Converts specific Sybase OEM System DSN
dsn The name of the DSN to be converted
/suffix This optional switch changes the way the DSNs are named. If this switch is used, the original
OEM DSN will retain its current name and the new DSN will be named ‘-’.
suffix The suffix that will be used to name the new DSN.
10 pROpeRties nOt MigRated
Following is a list of OEM properties not migrated in the current version; some of these may be supported in future
releases.
Also, appropriate warning messages are issued when a property cannot be migrated or when user attention is
directed to a specific situation where manual intervention is required; therefore, it is extremely important to review
and react if necessary to resultant messages:

OLEDB
The following OEM properties are not supported:
ODBC
ClsID
KB_Network_Authentication
KB_Mutual_Authentication
KB_DataIntegrity
KB_DataConfidentiality
KB_ReplayDetection
KB_OutOfSequence
InitializationString
TruncateTimeTypeFractions
UseSybaseLDAP
Row Cache Size
Extended ErrorInfo
Print Statement Behavior
Raise Error Behavior
Network Protocol
ProviderName
The following OEM properties are migrated as-is, but they are not supported by the organic driver:
of host:port pairs]
alternateservers [organic property alternateservers is used for SDC support which is a comma separated list
applicationusingthreads
connectionretrycount
connectionretrydelay
cursorcachesize
databases
distributedtransactionmodel
enabledescribeparam
interfacesfileservername
kb_dataconfidentiality
kb_dataintegrity
kb_mutual_authentication
kb_network_authentication
kb_outofsequence
kb_replaydetection
loadbalancing
networklibraryname
raiserrorpositionbehavior
reportcodepageconversionerrors
truncatetimetypefractions
useldaphaserver
usesybaseldap
xaopenstringparameters
5

6
11 autOMatic data sOuRce Backups
In order to preserve and allow users to refer to migrated OEM data sources, the migration tools automatically create a
backup of the migrated data source by adding the suffix ‘backup’ to the original name. For example, an OEM data source
named ‘Test’ will be migrated to Sybase as ‘Test’, and the original OEM data source will be renamed to ‘Test-backup’.
12 hOw tO MigRate a LaRge nuMBeR Of cLients
When your migration involves a large number of clients, it may not be practical to migrate each client individually
due to time constraints or in order to maintain consistency throughout the enterprise. Therefore, it is recommended
that in these scenarios the command line utility ‘dsnmigrate.exe’ be used in a batch procedure with the appropriate
argument to migrate either all, or the desired category, of data sources.
For example, the ‘/a’, ‘/ua’, and ‘/sa’ arguments provide for migrating groups of data sources. The /dsn argument can
be used to specify a specific data source for migration.
13 deveLOping new appLicatiOns using syBase OdBc and OLe dB pROvideRs
Developing applications using the Sybase drivers is consistent with developing applications using other OEM ODBC
and OLEDB drivers that are 100% compliant at the API level; therefore, an ODBC application, for example, written for an
OEM driver that is fully API compliant with the ODBC specification, will compile and run successfully with the Sybase
organic driver.
14 testing cOnsideRatiOns
As with any development project, it is highly recommended that customers test their applications prior to full
deployment in order to detect and rectify errors that may have been introduced in the migration process.
15 cOnnectiOn pROpeRty MatRix
For situations where the application developer needs to know the connection property names on “DSN-less”
connection strings, this matrix is provided as a matter of convenience.
The format will provide the property names as seen in the registry and the ODBC Data Source Administrator (GUI).
If the DataDirect property name in the GUI is different than the actual property name, the name will be provided in
parentheses.
For the Sybase ODBC Driver, property names are present in the registry in lowercase. In this matrix, mixed-case is
used for ease of reading. You can use mixed-case in a connection string.
In some cases, a sample value is provided for the Sybase Driver property.

ODBC Connection Property Compatible Names
OEM (Tabs from DSN) Sybase
General Tab
Description Description
NetworkLibraryName ---
NetworkAddress Data Source
Server and Port
Database Database
InterfacesFile DSURL
file://path_to_sql.ini\sql.ini
InterfacesFileServerName DsServiceName
Advanced Tab
RaiserrorPositionBehavior ---
DefaultLongDataBuffLen (KB) TextSize (Bytes)
DistributedTransactionModel DistributedTransactionProtocol
InitializationString InitializationString
ReportCodePageConversionErrors ---
XAOpenStringParameters ---
ApplicationUsingThreads ---
EnableQuotedIdentifiers QuotedIdentifier
EnableDescribeParam ---
TightlyCoupledTransactions TightlyCoupledTransaction
TruncateTimeTypeFractions ---
Connection
Databases ---
Default Login Id (LoginId) LogonId
WorkStationId ClientHostName
Charset Charset
ApplicationName ApplicationName
Language Language
PasswordEncryption EncryptPassword
Kerberos AuthenticationClient=
KB_Network_Authentication ---
KB_Remote_Principal ServerPrincipal
Performance
SelectMethod UseCursor
mitkerberos
OptimizePrepare (Prepare Method) DynamicPrepare
FetchArraySize FetchArraySize
PacketSize PacketSize
ConnectionCacheSize ---
cybersafekerberos
activedirectory
7

8
16 syBase ase data sOuRce adMinistRatOR
ASE ODBC Driver/OLE DB Provider Connection Properties
The format used to describe the connection properties includes the name of the property as used in the ODBC
Driver administrator, followed by the actual property name used in connection strings, surrounded in square brackets.
Example:
Enable High Availability [hasession/HASession]: [Descriptive text explaining the parameter]. Default [is|=] value.
The connection property name isn’t case sensitive. Lower case is equivalent to the conventional upper case for
initial letter of each word in the property. Words must be concatenated when the property is used in the connection
string for ODBC driver connection strings. The same goes with OLE DB Provider connection properties, unless you use
the generic properties such as “Initial Catalog”, “User ID”, etc.
Example ODBC Connection strings:
AseConnectionString = “{Driver = Adaptive Server Enterprise};UID=sa;PWD=xxx;Database=testdb;Server=asehost;
Port=5000;AnsiNull=1;UseCursor=1;DynamicPrepare=1;…..”
Another way to do this:
AseConnectionString = “{Driver = Adaptive Server Enterprise};uid=sa;pwd=xxx;database=testdb;server=asehost;
port=5000;ansinull=1;usecursor=1;dynamicprepare=1;…..”
Also, you can replace {Driver=…} with DSN=ase_DSN and include other properties to over-ride DSN settings.
Example OLE DB Provider Connection strings:
OleDbConnectionString = “Provider=ASEOLEDB;Server=aseHost;Port=5000;Initial Catalog=testdb;User
ID=sa;Password=xxx….”
OleDbConnectionString = “Provider=ASEOLEDB;Data Source=ase1502;User ID=sa;….”
The Sybase ASE Data Source Administrator (sybdrvadm.exe is a tool provided in the SDK under %SYBASE%\
DataAccess\bin or %SYBASE%\DataAccess64\bin for Winx64) so you can create OLE DB Data Sources. These are stored
in this same location by default as a text file with name of the Data Source followed by the extension “sod”. The Data
Source name without the “sod” extension is used in the “Data Source” connection property.

This enables an application to reference the OLE DB data source through the “Data Source” connection property.
Please note: The other panels are captured when configuring an ASE ODBC Driver with ODBC Driver Administrator
tool. The panels are the same as for the Sybase ASE Data Source Administrator. There are slight differences in how
the values are presented for selection. Shown here is the General tab from the Sybase ASE Data Source Administrator
configurator tool:
Compare it to the next page with the same panel used to configure the ODBC driver. (Service Name and BackEnd
Type are not available with OLE DB Provider.)
9

10
General Tab
Data Source Name: DSN as configured on the machine. This can be used as a logical reference to the data source.
Description: A description of this particular data source. Used primarily for documentation purposes.
Server Name (ASE Host Name) [server/Server]: Host where ASE resides.
Server Port [port/Port]: Listener port of the ASE.
Database Name [database/Database]: Default database for this data source connection.
Logon ID [uid/UID]: Default logon ID for the data source.
Service Name [servicename/ServiceName]: Not used for ASE. For DirectConnect server connections (MFC), this is the
access service name. (Not available with OLE DB Provider)
BackendType [backendtype]: Used for DirectConnect server (MFC) access service types (not available with OLE DB
Provider):
DC DB2 Access Service
DC TRS: Transaction Router Service
MFC gatewayless: When using OpenServerConnect on the Mainframe
Default is ASE.

Cursor Behavior
Use Cursors [usecursor/UseCursor]: When checked (unchecked by default) uses ASE Forward_only cursors for SELECT
statements.
Test Connection: After you configure your data source, press this button to test the ASE connection.
The fields are filled in with the values entered in the data source configuration. Press OK to connect to ASE.
11

12
Connection Tab
Login Time Out [logintimeout/LoginTimeout]: The time, in seconds, ODBC driver waits for a response from the ASE
after it sends the login request. After the time interval (15 seconds by default), the driver will issue a TDS attention
event, indicating to the ASE it no longer wants to wait for a response. The ODBC Driver will throw SQL_ERROR with
message “The command has timed out.”
High Availability Information
Enable High Availability [hasession/HASession]: (Unchecked by default) When checked, the ODBC Driver will set flag
on the login request to use ASE High Availability feature.
(Default = 0)
Alternate Servers [alternateservers/AlternateServers]: In establishing a connection, ODBC Driver by Sybase will first
try to connect to the primary host and port defined in the General tab of the Adaptive Server Enterprise dialog box.
If ODBC fails to establish a connection, ODBC will go through the list of hosts and ports specified in the Alternate
Servers field. Example entries:
Driver=AdaptiveServerEnterprise;server=server1;
port=port1;UID=sa;PWD=;HASession=1;
AlternateServers=server2:port2,...,serverN:portN;

When the primary server doesn’t response in the amount of time specified by LoginTimeout, the driver attempts to
connect to server2:port2, and so on, until it connects successfully or exhausts the list.
For information regarding the ASE Cluster Edition support refer to the New Features Open Server and SDK 15.0 for
Windows, Linux, and UNIX document, under ESD#12.
Server Name [secondaryserver/SecondaryServer]: The name or the IP address of the ASE server acting as a failover
server in an active-active or active-passive setup.
Server Port [secondaryport/SecondaryPort]: The port number of the ASE server acting as a failover server in an
active-active or active-passive setup.
Directory Service Information: This panel is used for alternate methods of determining the host and port for ASE
connectivity. This option allows for the use of an LDAP server or the interfaces file (SQL.INI for windows, interfaces
for LINUX).
URL [dsurl/DSURL]: The URL for the LDAP server, or the location to the interfaces file. Some examples are:
LDAP: ldap://hostport/dn[?attrs[?scope[?filter[?userdn?userpass]]]]
ldap://pvero-xp:389/dc=sybase,dc=com??one?sybaseServername=ase1252
Interfaces: file://[path][?][servicename]
file://C:\sybase\ini\SQL.INI
Service Name [dsservicename/DSServiceName]: The Service Name of the LDAP Sybase server object. The default is
an empty string.
User ID [dsprincipal/DSPrincipal]: The user name used to authenticate on the LDAP server, if the LDAP server does
not allow anonymous access. The principal can be specified in the DSURL as well.
Use Quoted Identifiers [quotedidentifier/QuotedIdentifier]: Specifies if ASE treats character strings enclosed in
double quotes as identifiers:
•0 = do not enable quoted identifiers (default)
•1 = enable quoted identifiers
Set ANSI Null [ansinull/AnsiNull]: Strict ODBC compliance where you cannot use “= NULL.” Instead, you must use
“IsNull.” Default is checked. Uncheck this if you use the “=NULL” in your SQL statements, especially the where clause.
(Default =1)
Enable Dynamic Prepare [dynamicprepare/DynamicPrepare]: When set to 1, the driver sends SQLPrepare calls to ASE
to compile/prepare. This can boost performance if you use the same query repeatedly. (Default =0)
Normalize Unicode Strings [normalizewcharparams/NormalizeWCharParams]: Under certain circumstances, when
the ASE is configured with “enable unicode normalization” set to 0, problems might occur with parameters set to TDS_
LONGBINARY. Setting this property to “1” will send the parameters as TDS_VARCHAR. Problem occurs with possible
error like:
“Attempt to insert NULL value into column ‘column name’, table ‘table name’; column does not allow nulls. Update
fails.”
Originally discovered with use of Microsoft Replication. (Default=0)
Cumulative Record Count [crc/CRC]: By default, the driver returns the total records updated when multiple update
statements are executed in a stored procedure. This count will also include all updates happening as part of any
triggers set on an update or an insert. Set this property to 0 if you want the driver to return only the last update
count. (Default = 1)
13

14
Ignore Errors if Results are Pending [ignoreerrorsifrspending/IgnoreErrorsIfRSPending]: Specifies whether the driver
is to continue processing or stop if error messages are present. When set to 1, the driver will ignore errors and continue
processing the results if more results are available from the server. When set to 0, the driver will stop processing the
results if an error is encountered even if there are results pending. (Default = 0)
Encrypt Password [encryptpassword/EncryptPassword]: Specifies if password encryption is enabled:
0 indicates password encryption is disabled,
1 indicates password encryption is enabled.
(Default = 0)
Security Tab
Secure Socket Layer
This is used to enable SSL so the driver can connect to an ASE configured for SSL.
Use SSL Encryption [encryption/Encryption]: The designated encryption. Possible values: ssl.
(Default = empty)
Trusted File [trustedfile/TrustedFile]: If encryption is set to ssl, this property should be set to the path to the Trusted
File. (Default = empty)

Kerberos
This is used for ASE configured to use Kerberos.
Authentication Client [authenticationclient/AuthenticationClient]: Enables Kerberos authentication using one of
these Kerberos providers (Default = empty, selecting none):
mitkerberos
cybersafekerberos
activedirectory
User Principal [userprincipal/UserPrincipal]: The user principal as configured in the Key Distribution Center (KDC).
This is optional.
Server Principal [serverprincipal/ServerPrincipal]: The logical name or the principal as configured in the Key
Distribution Center (KDC).
The ASE ODBC driver will use this information to negotiate Kerberos authentication with the configured KDC and
ASE server.
Advanced Tab
Buffer Pool Size [buffercachesize/BufferCacheSize]: Keeps the input / output buffers in pool. When large results will
occur, increase this value to boost performance. (Default = 20)
Text Size [textsize/TextSize]: The maximum size of binary or text data, in bytes, that will be sent over the wire.
(Default = none, uses ASE default of 32768 bytes)
15

16
Application Name [applicationname/ApplicationName]: The name used by ASE to identify the client application.
(Default = none)
Client Host Name [clienthostname/ClientHostName]: Name of client host running the application using the ODBC
Driver. This value must be populated if you want to use it.
Client Host Process [clienthostprocess/ClientHostProcess]: This value is actually determined internally and
automatically. It is the value of the process id belonging to the application using the ODBC Driver. This shows up in
the TDS Login token and under the hostprocess column on the ASE sysprocesses table.
Fetch Array Size [fetcharraysize/FetchArraySize]: Specifies the number of rows the driver retrieves when fetching
results from the server. (Default = 25)
Initialization String [initializationstring/InitializationString]: Session related SQL statements that can be sent to the
ASE upon login time. Examples are set statements:
set transaction isolation level 1 set textsize 64000 ….
Language [language]: The language in which ASE returns error messages. (Default = empty, ASE uses English by
default)
Character Set [charset/CharSet]: Determines what character set is used for character translation between the client
and ASE.
User Specified: Enter the value to use if different from ASE. Example, if ASE is set to use iso_1 character set, and
client wants to use cp850, then check this item and enter value “cp850”. This sets charset=cp850.
Server Default: Upon login negotiation client uses character set specified by the ASE. This sets
charset=ServerDefault.
Client Default: When this is selected, charset=ClientDefault, and this uses the charset based on the operating
system settings. In this case, another property is set, [codepagetype/CodePageType] and is set to either ANSI (ansi) or
OEM (oem).
Packet Size [packetsize/PacketSize]: When Server Packet Size is checked, this sets enableserverpacketsize/
EnableServerPacketSize to 1 [on by default], which enables ASE 15.0 or higher to choose an optimal packet
size. The PacketSize property defaults to 512 bytes. When the property Restrict Maximum Packet Size
[restrictmaximumpacketsize/ RestrictMaximumPacketSize] is set, ASE can only optimize to this value, unless ASE
maximum packet size is less than this value, which is set in the dialog for Server Packet Size, and is actually set in the
PacketSize property. Therefore, if the Server Packet Size dialog is set to 2048, then PacketSize=2048.

Transaction Tab
Server Initiated Transactions [serverinitiatedtransactions/ServerInitiatedTransactions]: When SQL_ATTR_
AUTOCOMMIT is set to “1” Adaptive Server starts managing transactions as needed. The driver issues a “set chained on”
command on the connection. Older ODBC Drivers do not use this feature and manage the job of starting transactions
by calling begin tran. Set this property to “0” if you want to maintain the old behavior or require that your connection
not use “chained” transaction mode. (Default = 1)
Distribute Transactions: Used when ASE/DTM (Distribute Transaction Manager) is used on the ASE, which requires
an ASE_DTM license.
Tightly Coupled Transactions [tightlycoupledtransaction/ TightlyCoupledTransaction]: (Windows only) When using
distributed transactions, if you are using two DSNs which connect to the same ASE server, set this to 1. See “Using
Distributed Transactions” on page 41, in Chapter 3, “ASE Advanced Features.” (Default = 0)
Distributed Transaction Protocol [distributedtransactionprotocol/ DistributedTransactionProtocol]: Allows the
driver to use either an XA protocol or OleNative protocol when using distributed transactions. See “Using Distributed
Transactions” on page 41, in Chapter 3, “ASE Advanced Features.” This is either of two values: XA or OLE. For windows
clients only. (Default = XA)
17

18
About Tab
This panel provides file (sybdrvodb.dll) version information. Driver Name is always “Adaptive Server Enterprise”.
Driver Version relates to the file version of the sybdrvodb.dll. Driver ODBC Version is the version of ODBC API used with
this driver.
17 uninstaLLing OeM pROducts
After successfully migrating to Sybase’s ODBC driver and OLE DB Provider, uninstalling and removing the OEM
products will be necessary if you don’t wish to retain these older products. This section explains how this can be done
manually if uninstalling doesn’t work with the old SDKs.
Sybase ASE ODBC Driver
There are two areas to work with here, the files and the registry. For the files, the default location is %SYBASE%\
ODBC. There are no newer files from the ASE ODBC Driver installed here. When you’re satisfied that your migration
went well and you have good backups of the system and the older ODBC folder, you can remove the folder and its
contents.

In the above diagram %SYBASE% = C:\Sybase\ocs\syb1251.
PLEASE NOTE: Be extremely careful when modifying the registry. Make sure you have a current backup before you
do any deletions of the OEM ODBC driver.
DSN Removal
You can remove DSNs from the registry directly or by using the ODBC Data Source Administrator tool (ODBCAD32.
exe). It’s recommended that you use the admin tool as it does a good job of removing the DSN from the registry.
Simply look for your DSNs under the User and System tab, select the DSN and remove them with the “Remove” button.
You need to be aware of all your User and System DSNs as well as possible File DSNs.
The User and System DSNs are located in the registry under HKCU\Software\ODBC\ODBC.INI for User DSNs and
HKLM\Software\ODBC\ODBC.INI for System DSNs. Each active DSN is listed as a folder under the ODBC.INI folder.
If you remove the folder here from the registry be aware there’s also another folder under ODBC.INI, “ODBC Data
Sources”:
Under this folder, look for the DSNs on the right with Data of “Sybase ASE ODBC Driver” and the Name of your
targeted DSN. Once you remove the DSNs in this manner, they’ll no longer be available on the system.
Another recommendation is to make sure you use the migration tool (Chapter 8) so you can use the same DSN
names for your applications. Once you’re satisfied everything works you can remove the renamed DSN.
19

20
ODBC Driver removal
To handle the ODBC driver registry information there are two areas to work with: The Driver and the DSN (Data
Sources). The driver name is “Sybase ASE ODBC Driver”. In the registry this folder is located under:
HKLM\Software\ODBC\ODBCINST.INI\Sybase ASE ODBC Driver
This folder contains various items related to the ODBC Driver and in particular the folder location. If you are unsure
of where the Sybase ASE ODBC Driver is installed, look here. Once this is removed you’ll be unable to create new
Sybase ASE ODBC Driver DSNs.
To finish with the driver removal, also remove the item under “HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers”:
The item is “Sybase ASE ODBC Driver”. Once this is removed, as well as the aforementioned “Sybase ASE ODBC
Driver” folder, you’ll no longer be able to see it on your system, nor will you be able to create DSNs as “Sybase ASE
ODBC Driver”.
Lastly, you can remove the %SYBASE%\ODBC folder from the PATH statement. It’s not a requirement but it’ll free up
space on the variable.
OEM OLE DB Provider removal
The removal of the OEM OLE DB Provider, “Sybase ASE OLE DB Provider”, is not as difficult. There are two steps to the
task. The assumption here is that the user has already migrated the data sources to the SOD file extension (with the
migrating tool), and now wishes to remove the Sybase ASE OLE DB Provider.

The default install location is %SYBASE%\OLEDB. The first thing to do is to un-register the provider using the
regsvr32.exe utility, included in the Windows operating system. To do this, cd to the %SYBASE%\OLEDB folder,
then issue:
REGSVR32 /u SYDAASE.DLL
The next step is to remove the data sources and the files. By default the data source files and *.IDS files are located
in the %SYBASE%\OLEDB folder. There’s a possibility the IDS files are located in an alternate folder. You can check this
by running the Sybase ASE OLE DB Configuration Manager utility, sydaadm.exe, found in %SYBASE%\OLEDB.
Select the “Tools” | “Options” | “Main Data Source Directory” options from the menu. You’ll see something like this:
If the current directory displayed is different from %SYBASE%\OLEDB, you need to take note of this and remove it
when you’re ready.
The last thing to do is to remove the %SYBASE%\OLEDB directory:
Once this is all done, you can remove the %SYBASE%\OLEDB folder from the PATH environment variable. This frees
up space for products that require folders to be on PATH such as the ASE ODBC Driver and ASE OLE DB Provider.
21

Sybase, Inc.
Worldwide Headquarters
One Sybase Drive
Dublin, CA 94568-7902
U.S.A
1 800 8 sybase
www.sybase.com
As a review, the steps to remove the OEM products are to cleanup the registry, remove the old files and remove
the folders from the system PATH environment variable. You’ll want to make sure you’re ready for this after your
migration. Make sure you have current backups before you proceed with the removals.
18 RefeRences
The following references might be of further assistance in the migration process.
• “Migration Mania: Tips for Migrating ASE ODBC Driver and OLE DB Provider”; ISUG Technical Journal, Issue #5,
Sep/Oct, 2007.
• “New Features Open Server 15.0 and SDK 15.0 for Microsoft Windows, Linux and UNIX”; http://infocenter.sybase.
com/help/index.jsp?topic=/com.sybase.dc20155_1500/html/newfesd/title.htm&toc=/com.sybase.help.sdk_15.0/
toc.xml
• “ASE 15.0 ODBC Driver by Sybase User’s Guide”;
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20116_1500/html/aseodbc/title.htm&toc=/
com.sybase.help.sdk_15.0/toc.xml
• “ASE 15.0 OLE DB Provider User’s Guide”;
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc00075_1500/html/oledb/title.htm&toc=/com.
sybase.help.sdk_15.0/toc.xml
Copyright © 2009 Sybase, Inc. All rights reserved. Unpublished rights reserved under U.S. copyright laws. Sybase and
the Sybase logo are trademarks of Sybase, Inc. or its subsidiaries. All other trademarks are the property of their respective
owners. ® indicates registration in the United States. Specifications are subject to change without notice. 03/09