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

Converting SQL/MP Applications to SQL/MX

Applications

HP NonStop SQL/MX Database and Application Migration Guide—540435-005

10-61

Steps for Moving an Application to Production

1. On the production system, run UPDATE STATISTICS commands:

•

For each SQL/MP database object that your SQL/MX application accesses,

run the SQL/MX UPDATE STATISTICS command and then the SQL/MP

UPDATE STATISTICS command.

To avoid possible locking problems, do not run the SQL/MP UPDATE

STATISTICS command and the SQL/MX UPDATE STATISTICS command at

the same time on the same object.

•

For each SQL/MX database object that your SQL/MX application accesses,

run the SQL/MX UPDATE STATISTICS command.

Run UPDATE STATISTICS as a low-priority background process or when peak

database performance is not required. UPDATE STATISTICS takes longer to run

for larger tables. To reduce the run time of UPDATE STATISTICS for large tables,

use the SAMPLE clause. For more information about UPDATE STATISTICS, see

the

SQL/MX Reference Manual.

2. Set up class MAP DEFINEs in the production environment to ensure proper name

resolution.

3. Create SQL/MP aliases in the production environment to ensure proper name

resolution.

4. Move the program files and any module definition files, if they exist for embedded

SQL/MX applications, to the production environment.

5. Generate new module files for embedded SQL/MX applications in the production

environment.

6. At an optimal cutover time, bring down the SQL/MP application and start the new

SQL/MX application.

For details about moving an application from development to production, see the

SQL/MX Installation and Management Guide.