Oracle to Sybase ASE Migration Guide

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3Domain knowledge of the business application(s), system and environment. It is essential to have a full andcomplete understanding of all applications that access the Oracle database being migrated. This includes theclient applications that connect to the Oracle database directly, but also applications that indirectly access thedatabase, for example through an application server.For all these applications, it needs to be understood which data the application accesses in the database, andhow it modifies such data. Any SQL code submitted to the database by the application must be identified, aswell as how such SQL code can be changed.Availability of sufficient Oracle expertise to analyze all aspects of the database is an absolute requirement. Akey activity is to identify which specific Oracle features are used (as per the checklists in chapter 3), especiallythose which do not have a direct Sybase equivalent.Full access to all Oracle PL/SQL code being used, both in the database and in all client applications.As a minimum, sufficient understanding of Sybase ASE in order to create a functionally working migrateddatabase system. At a later stage in the migration project, more specialized Sybase expertise will likely beneeded for Sybase ASE-specific performance tuning and optimization. Having such expertise available at anearly stage may be helpful.A comprehensive testing process and production-like environment for validating the migration approach andthe affected software applications against the migrated Sybase database. For best results, it is highlyrecommended to use a copy of production data (as close as possible) as well as hardware which is similar in sizeto production.2.3 Not covered by this guide: Project aspectsThis Migration Guide does not prescribe or suggest how to organize a migration project in terms of preparation, settingup testing procedures, validating the migrated components, etc. These aspects of a migration project are left torequirements, standards, best practices and preferences of the organization undertaking the emigration effort.Please note that the absence of specific recommendations for testing and validation of migrated components does notmean that such activities should not be performed. On the contrary, these activities are essential, and it is recommendedto follow generally accepted best practices with respect to software testing and validation.2.4 Not covered by this guide: Sybase ASE-specific tuningThe primary purpose of this Migration Guide is to assist in creating a functionally equivalent Sybase ASE-based systemcompared with the original Oracle-based system. The purpose of this Migration Guide is not to provide guidance forarriving at an optimally tuned Sybase ASE system; while Sybase ASE-specific tuning will likely be necessary as part of amigration project, this Migration Guide deliberately makes no attempt to cover such tuning aspects.Since ASE-specific tuning is considered to be mostly unrelated to any Oracle-specific aspects or considerations, thereader is referred to the Sybase ASE documentation for background and recommendations about Sybase ASE tuning.,specifically the System Administration Guide and the Performance and Tuning manuals.How to use this Migration Guide 7