ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

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.