SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)
Version Management and Interoperability
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
3-3
Naming Scheme for SQL/MX Releases
Naming Scheme for SQL/MX Releases
NonStop SQL/MX contains many individual products, which are identified by
T-numbers. A SQL/MX release name identifies a set of SQL/MX products as belonging
to a given release of NonStop SQL/MX.
Each SQL/MX release is identified by a three-part release identifier:
1. The first number indicates a
major release, which introduces major new
functionality and a new SQL version.
2. The second number indicates an incremental release, which introduces an
incremental change and some new functionality.
3. The third number indicates a
maintenance release, which introduces bug fixes and
minimal new functionality.
The migration risk increases from maintenance to major releases because major
releases introduce significant new functionality that makes fallback more difficult, if
implemented.
The first and second levels of the release name (for example, SQL/MX Release 3.0)
are based on the product version identifier (for example, H30). Major and incremental
releases typically change the product version of NonStop SQL/MX. Maintenance
releases and time-critical fixes (TCFs) do not change the product version of NonStop
SQL/MX.










