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

Overview of SQL/MX Migration
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
1-10
Assessing Your Current Application and Database
Environment
Use the information that you gather in Table 1-3 to help you define the best migration
path to meet your business needs. Next, start Assessing Your Current Application and
Database Environment on page 1-10.
Assessing Your Current Application and Database Environment
To plan migration to NonStop SQL/MX, start by assessing the application and database
environment on the current system to:
•
Determine what applications will be affected by the migration and what changes
you will need to make to complete a successful migration to NonStop SQL/MX.
•
Obtain performance information about the current system, including CPU loads,
disk drive usage, and application and database performance. All this information
provides a reference point for setting and achieving performance objectives for the
migrated applications and database.
Use these tables to gather information about your current application and database
environment:
•
Table 1-4, System Configuration, on page 1-11
•
Table 1-5, Database Applications, on page 1-12
•
Table 1-6, Application Execution Environment, on page 1-13
•
Table 1-7, Development Environment, on page 1-13
•
Table 1-8, Testing Environment, on page 1-14
•
Table 1-9, Database, on page 1-14
What are the skills of the technical
staff assigned to the migration?
What is the program cost for training
the technical staff?
What is the cost of managing the
project?
What is the cost of acquiring new
software and/or hardware?
What is the cost of developing new
applications?
What is the cost/resource threshold
for the migration? (What would be
considered too large an effort to
move forward with the migration?)
Table 1-3. Determining Your Business Objectives (page 2 of 2)
Obtain this information