SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Preparing to Migrate From SQL/MX Release 1.8 to
SQL/MX Release 2.x
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
5-2
Planning for Performance and Capacity
an RVU that supports SQL/MX Release 1.8 (G06.18 through G06.22) before migrating
to SQL/MX Release 2.x (G06.23 or later).
Planning for Performance and Capacity
Before migrating to SQL/MX Release 2.x, use Measure to obtain initial baseline data,
such as average query run time, CPU time, and process time. At each phase of the
migration, gather the same type of data and analyze it. For more information about
Measure, see the
Measure User’s Guide. For more information about using Measure
during migration, see Guidelines for Conducting the Migration
on page 1-19.
Before migrating your database to SQL/MX Release 2.x, check that you have
adequate disk space. SQL/MX Release 2.x creates more metadata tables but should
use approximately the same space that already exists for NonStop SQL/MP. SQL/MX
Release 2.x will also use more OSS space. For minimum disk space requirements for
SQL/MX Release 2.x, see the
SQL/MX Installation and Management Guide. The Disk
Space Analysis Program (DSAP) can help you analyze the use of space on disk
volumes. For more information about DSAP, see the
Guardian Disk and Tape Utilities
Reference Manual.
Planning for Fallback
Before you migrate to SQL/MX Release 2.x, plan for a potential fallback to SQL/MX
Release 1.8. To ensure that you can fall back more easily, follow these guidelines:
•
Installing Fallback SPRs on page 5-3
•
Planning New Feature Implementation on page 5-3
•
Keeping SQL/MP Metadata Tables on page 5-4
If you encounter a serious problem with a newer version of SQL/MX Release 2.x and
need to fall back to a previous version of SQL/MX Release 2.x, see Section 4, Falling
Back to an Earlier Version of SQL/MX Release 2.x.
Note. If you encounter the problem when using new features that are specific to SQL/MX
Release 2.x, consider discontinuing the use of those features instead of falling back from that
database environment.