
Migrating to Sybase Adaptive Server Enterprise 11.5 4-7
Adaptive Server Enterprise 11.5 Determine Migration Approach
Phased Cutover
The issues for a phased cutover are:
Table 4-4: Phased cutover migration
Issue Recommendations and Tips
Method Change only one application and database to release 11.x at a time.
Fallback Consider making daily bcp dumps of the databases. To fall back, you can then
load the dumps into release 10.x or 4.x. Keep in mind:
• You may need to modify the databases to support incremental bcp dumps.
• Pre-release 11.x cannot read release 11.x backup files. You need to create bcp
or other scripts to move tables back to pre-release 11.x.
• Do not use release 11.x schema enhancements, such as max_rows_per_page,
declarative RI (referential integrity) and IDENTITY columns, until the
conversion succeeds.
For information about scheduling backups of user databases, see the System
Administration Guide.
Application test suite Ensure that the application test suite addresses both update correctness and
performance acceptability. Also ensure that you do the following:
• Maintain the directories/libraries for both releases.
• Make sure the applications are using the correct server.
• After successful validation, consider having users enter production queries
with the production toolset. A good time to do so is after hours or during
production lulls.
See Chapter 7, “Test: Ensuring Stability and Performance” for more
information on testing.
Bridging There should not be any user impact during migration. The more stringent the
validation test is, the less likely you will have bridging issues.
Pre-release 11.x cannot read release 11.x backup files. You need to create bcp or
other scripts to move tables back to pre-release 11.x.
Note: Do not use release 11.x schema enhancements, such as max_rows_per_page,
declarative RI and IDENTITY columns, until the conversion succeeds.
Comentarios a estos manuales