SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-12
C-Series to D-Series Migration Considerations
If you are migrating from version 1 to a version 300 or newer version, you can use
these version 2 features without upgrading any version 1 catalogs: parallel
execution, local autonomy, parallel index maintenance, and virtual sequential block
buffering.
You can have a combination of versions of catalogs on a node. Unless you have
an important reason for keeping this combination (such as operating in a mixed-
version network), you should eventually upgrade all the catalogs on the node to
simplify your database management efforts.
For additional information, see Upgrading Catalogs on page 2-14.
2. Recompile applications if desired. You do not need to SQL compile your
application programs unless you want to take advantage of new features or
performance enhancements.
To take advantage of new features, you might have to modify your programs. For
example, versions 325 and newer software support CASE expressions. To use
them, you need to modify source code and then host-compile and SQL compile the
modified programs by using the newer versions of the SQL/MP compilers. For
more information, see the SQL/MP Programming Manual.
To take advantage of performance enhancements, host-compile and SQL compile
existing programs to ensure that the execution plan is optimal for the new SQL/MP
software. For example, versions 310 and newer SQL compilers generate query
execution plans that provide better performance than plans generated by older-
version SQL compilers.
With the exception of a dynamic SQL program that does not use the RELEASE
option, a program written for an older version of the SQL/MP software should
compile and execute on a node that has version 310 or newer software with no
source code changes.
C-Series to D-Series Migration Considerations
If your previous installation of SQL/MP was on a node that ran a C-series RVU of the
operating system, you should be aware of differences between the C series and D-
series systems that affect the operation of SQL/MP.
The D-series features that might affect your SQL/MP applications are high and low
process identification numbers (PINs), changes to file naming rules, and subvolume
defaulting. In addition, you must understand the rules for combining C-series and
D-series object modules.
For more information about D-series features, see the D-Series System Migration
Planning Guide.