ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

More documents

Recommendations

Info

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
Page 1: white papeR ASE ODBC Driver and OLE
Page 5 and 6: 5 suppORted pLatfORMs The ASE OLE D
Page 7 and 8: OLEDB The following OEM properties
Page 9 and 10: ODBC Connection Property Compatible
Page 11 and 12: This enables an application to refe
Page 13 and 14: Cursor Behavior Use Cursors [usecur
Page 15 and 16: When the primary server doesn’t r
Page 17 and 18: Kerberos This is used for ASE confi
Page 19 and 20: Transaction Tab Server Initiated Tr
Page 21 and 22: In the above diagram %SYBASE% = C:\
Page 23 and 24: The default install location is %SY

ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

Create successful ePaper yourself

Delete template?

Save as template?