SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Converting an SQL/MP Database to SQL/MX Tables
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
11-7
Distributed Database Objects
collections of schemas. Schema names must be unique within a given catalog. Multiple
objects with the same name can exist in a schema provided that each name belongs to
a different namespace. NonStop SQL/MX supports various namespaces, such as table
value objects (tables, views, stored procedures, and SQL/MP aliases), indexes, and
triggers. For more information about namespaces, see the
SQL/MX Reference Manual.
Distributed Database Objects
Both NonStop SQL/MP and NonStop SQL/MX support distributed database objects. In
NonStop SQL/MP, you must define a catalog on a node to describe the partition
resident on that node. Partitioned tables and indexes must have their descriptions
stored in the catalog on each node where their partitions reside. This duplication of the
table or index description enables local node autonomy.
In NonStop SQL/MX, you register the catalog of an SQL/MX database object on
remote nodes to make that catalog and its database objects visible on the remote
nodes. NonStop SQL/MX does not replicate the metadata of an SQL/MX database
object on each node where the object is partitioned. The SQL/MX metadata resides
only on the node where the SQL/MX database object was created. Therefore, NonStop
SQL/MX has limited local node autonomy for distributed databases. For more
information about managing a distributed SQL/MX database, see the SQL/MX
Installation and Management Guide.
Database Object Security
In NonStop SQL/MP, Guardian security and the optional Safeguard security
management facility provide authorization to operate on SQL/MP database objects and
applications in the Guardian environment. NonStop SQL/MP uses the SECURE
clause, which specifies a Guardian security string,
"rwep", to secure SQL/MP
database objects.
Guardian security and Safeguard security are not applicable to SQL/MX database
objects. Safeguard rules for Guardian files are not enforced for SQL/MX files. Security
for an SQL/MX database object is set at the time of object creation and is independent
of Safeguard security settings. NonStop SQL/MX uses its own security mechanism to
authorize access to SQL/MX database objects and does not use a Guardian security
vector stored in a file label.
The SQL/MX GRANT and REVOKE statements, which conform to the ANSI SQL
standard, control privileges for SQL/MX database objects. These privileges are stored
in the SQL/MX metadata tables and the underlying file labels. In NonStop SQL/MX, if
you do not explicitly grant privileges for an SQL/MX database object, only the owner
has privileges on the SQL/MX database object. In NonStop SQL/MX, the super ID
(Guardian user ID 255,255) is considered an owner of all SQL/MX database objects
and has complete privileges on all SQL/MX database objects. For more information
about GRANT, REVOKE, and SQL/MX privileges, see the
SQL/MX Reference Manual.
In NonStop SQL/MX, most SQL/MX application files are stored in the OSS
environment, which adheres to OSS security rules. The module files of embedded