SQL/MP Version Management Guide
Database Versions
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
3-3
Relation of Catalog Version to Software Version
For example, you can create version 315 user catalogs registered in a version 1 or 
version 2 system catalog on a node running version 315 software. You cannot, however, 
use a version 315 system catalog on a node running version 2 software. 
Figure 3-2
 illustrates the relationship of the system catalog to user catalogs on a node 
running version 315 software.
Relation of Catalog Version to Software Version
As shown in Figure 3-2, the version of an existing user and system catalog can be the 
same as (or older than) the version of the software running on the same node. However, 
when you create a new catalog, the new catalog is assigned the same version number as 
the software on the node where the catalog resides. 
For example, suppose there is a version 2 system catalog on a node running version 310 
software. If you create a new user catalog on that node, the catalog is version 310, and 
your new version 310 catalog is registered in the existing version 2 system catalog. 
It is not necessary to upgrade existing catalogs when you install a new version of 
SQL/MP software. However, to create tables or other objects that have features of the 
new version, or to run programs that use new features, you must either upgrade the 
existing catalog in which the object is to be registered or create a new catalog. 
For example, when you install version 310 software on a node, you can also create a 
version 310 catalog on that node and register new objects in that catalog. You can then 
continue running existing programs using existing version 1 or version 2 catalogs while 
you test new version 310 features using the new version 310 catalog.
Initializing and Changing User Catalog Versions
You initialize the version of a catalog when you create the catalog. You can change the 
version of a catalog by executing the UPGRADE CATALOG or DOWNGRADE 
CATALOG statement (for a user catalog), or the UPGRADE SYSTEM CATALOG or 
DOWNGRADE SYSTEM CATALOG statement (for a system catalog). 
Figure 3-2. Relationship of System Catalog to User Catalogs
V1 Objects
Version 1
User Catalog
Version 315
User Catalog
Node Running
Version 315 NonStop(TM) SQL
Version 2
System Catalog
Version 2
User Catalog
VST006.vsd
V1 Objects
V2 Objects
V1 Objects
V2 Objects
V300 Objects
V310 Objects
V1 Catalog
V2 Catalog
V300 Catalog
V310 Catalog
V315 Catalog










