SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Managing an SQL/MX Distributed Database
HP NonStop SQL/MX Installation and Management Guide—523723-004
13-3
SQL/MX Distributed Database Features
•
To increase local computing power by the aggregate total of the computing power
of the network.
SQL/MX Distributed Database Features
For NonStop SQL/MX Release 2.1 or Release 2.0, users can:
•
Register a user catalog on nodes other than the node where the catalog was
created. The object metadata for the catalog remains on the original node. Each
registered node then can locate the object metadata for that catalog. The catalog is
“visible” on those nodes. For more information, see Creating, Registering, and
Unregistering Catalog References on page 13-19.
•
Execute statements and commands that operate on database objects in catalogs
that are visible from the node where the statement or command is executed.
•
Distribute database objects to nodes where the objects’ catalogs are visible.
Database distribution is largely transparent to users of NonStop SQL/MX. Most of its
features are implemented at levels that make transparency possible. These features
include:
•
Versioning Capabilities on page 13-3
•
User Data Distribution on page 13-4
•
Catalog Reference on page 13-4
•
ANSI Name Lookup on page 13-4
•
Visibility Rules on page 13-5
•
Transparency on page 13-5
•
Security Guidelines on page 13-6
•
Local Autonomy on page 13-6
Versioning Capabilities
The nodes in a distributed SQL/MX database can run different releases of SQL/MX
software. Each release of SQL/MX software can identify the other releases that it is
compatible and incompatible with. The SQL/MX versioning design ensures that:
•
Nodes with compatible software versions can interoperate.
•
Access to or from nodes with incompatible software versions fail predictably.
Release 2.1 and Release 2.0 do not support interoperability with Release 1.8 in a
distributed database environment. You cannot perform queries—through embedded
SQL or dynamic SQL—from a node running Release 2.1 or Release 2.0 on a node
running Release 1.8, and vice versa.
For more information about versioning issues for Release 2.1 and Release 2.0, see
Versioning Issues on page 1-12.