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

Upgrading to a Newer Version of SQL/MX Release
2.x
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
3-2
Implementing New Functionality
3. Install, configure, and start the HP NonStop Transaction Management Facility
(TMF), which must be running on the system node where you install NonStop
SQL/MX. For more information, see the
TMF Planning and Configuration Guide.
4. Install NonStop SQL/MX. For more information, see the
SQL/MX Installation and
Management Guide.
5. Apply any fallback SPRs that are required for falling back from SQL/MX Release
2.2 or SQL/MX Release 2.1. For more information, see the SQL/MX Master
Softdoc (T0650).
6. Consider upgrading other nodes in a distributed database network to the same
version of SQL/MX Release 2.x. For more information, see Managing a Mixed-
Version Network on page 2-15.
Implementing New Functionality
If there is any chance of falling back to a previous SQL/MX Release 2.x, you should
defer implementing new functionality and recompiling SQL/MX applications and user
modules until you are sure that fallback is unlikely.
When you are confident that fallback will not be necessary, you can start implementing
new SQL/MX Release 2.x features and recompiling SQL/MX applications and user
modules. To learn about the new functionality and enhancements in a particular
version of SQL/MX Release 2.x, see the SQL/MX Master Softdoc (T0560) for that
particular release.
Even if you choose not to implement new features, consider recompiling the SQL/MX
applications and user modules with the new version of SQL/MX Release 2.x. SQL/MX
Release 2.1 introduces faster expressions for some types of queries than SQL/MX
Release 2.0. Therefore, some SQL/MX Release 2.2 and Release 2.1 query execution
plans will show better performance than comparable SQL/MX Release 2.0 plans. For
information about these performance enhancements, see the
SQL/MX Query Guide.