NonStop NS-Series Database Migration Guide

Preparing to Migrate to an Integrity NonStop
NS-Series System
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
1-7
Plan the New System’s Applications and Database
Environments
Plan the New System’s Applications and Database
Environments
After you have thoroughly assessed the NonStop S-series system’s applications and
database environments, use the information to begin planning for these environments
on the Integrity NonStop NS-series system.
Table 1-3 describes the information you would use to plan the applications and
database environments on the Integrity NonStop NS-series system platform.
All NonStop
database
environments
•
Databases and data files that are candidates for migration. Provide
high-level information about their size, location, and performance.
•
For the Guardian and OSS environments, all significant flat-file use by
application. For the OSS environment, identify character-file use and
the number of mount points for the file system.
SQL/MP or
SQL/MX
database
•
The release of NonStop SQL/MP or NonStop SQL/MX installed on the
system
•
Number of SQL-compiled programs
•
Number of SQL/MP or SQL/MX tables
•
For each SQL/MP or SQL/MX table, its file size and number of views
and partitions
•
For each SQL/MP or SQL/MX table, all primary keys, indexes,
columns, and partitions. For SQL/MX tables, describe any use of the
SQL/MX buffer for query plan caching.
•
Information about table statistics
•
Information about query plans to use for evaluation and subsequent
comparison with query plans on the new system
•
Stored procedures in Java (SPJs), triggers within local and foreign
catalogs, ODBC, JDBC/MX, large objects, and database access
middleware
Enscribe
database
•
Number of Enscribe files
•
For each Enscribe file, its size and number of partitions
Table 1-2. Assessing the Applications and Database on the Current
System (page 3 of 3)
For this
environment Obtain this information