SQL/MP Version Management Guide

Database Versions
Compaq NonStop™ SQL/MP Version Management Guide—429833-001
3-9
SQL Object Versions
GET CATALOG OF SYSTEM Statement
You can execute the GET CATALOG OF SYSTEM statement from a static SQL
program, but not from a dynamic SQL program. Alternatively, you can enter GET
CATALOG OF SYSTEM as a command by using the SQLCI command interface. The
statement returns the name of a local or remote system catalog.
The GET CATALOG OF SYSTEM statement is not available to version 1 or version 2
SQL software; you must enter the statement from a node running version 300 or newer
software. In a network, you can issue the GET CATALOG OF SYSTEM statement to
retrieve the name of a catalog on a remote node, even if the software on the remote node
is an older version.
For example, suppose you are running version 310 SQLCI on a node named \SYS2. To
determine the name of the system catalog on a remote node named \SYS1, you can
execute the GET CATALOG OF SYSTEM statement. Then you can retrieve the version
of the remote catalog by executing the GET VERSION OF CATALOG statement.
This code fragment illustrates the use of these commands and shows their results:
>> GET CATALOG OF SYSTEM \SYS1;
CATALOG: \SYS1.$VOL1.SQL
--- SQL operation complete.
>> GET VERSION OF CATALOG \SYS1.VOL1.SQL;
VERSION 2
--- SQL operation complete.
You cannot execute the EXECUTE IMMEDIATE statement with the GET CATALOG
OF SYSTEM statement.
For the syntax of the GET CATALOG OF SYSTEM statement and for examples of
using this statement in a static SQL program, see the NonStop SQL/MP Reference
Manual and the NonStop SQL/MP Programming Manual for the language you are using.
SQL Object Versions
An SQL object is a table, view, index, collation, or constraint. Neither a catalog nor a
program is considered to be an SQL object.
The features associated with an SQL object determine its version. For example, a table
with a clustering key is a version 2 object, while the version of a table that uses
collations or multibyte characters is 300 or newer. For a complete list of the features that
determine object versions, see Appendix A, Summary of Feature, Catalog, and Data
Structure Changes.
Versions of SQL objects are affected by versions of related SQL objects. For example,
the object version of a table can be affected by the versions of any indexes, constraints,
and collations associated with the table. For more information about object-version
dependencies, see Object-Version Dependencies
on page 3-15.
Object version numbers can be used to determine whether a particular version of the
SQL/MP software supports a particular object. SQL/MP does not support an object
unless the object’s version is the same as or older than the version of the software.