SQL/MP Installation and Management Guide

Creating a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
5-10
Securing the System Catalog
Securing the System Catalog
The system catalog maintains the directory of catalogs on each system in the
CATALOGS table. Except for this table, the system catalog is like any other catalog on
the system. You can use the system catalog as a catalog directory only or as a
general-purpose catalog.
The security of the system catalog should protect the catalog from removal.
CATALOGS Table
For a user to create other catalogs on the system, the user must have authority to write
to the system directory of catalogs, the SQL.CATALOGS table. You can secure this
table separately from the rest of the system catalog to restrict the capability to create
catalogs within your application.
You might consider giving read authority to all users, enabling them to query the
SQL.CATALOGS table.
Examples
This example shows catalog security that ensures that catalogs can be created only by
the local database administrator’s group (DBA.Super, DBA.Dev, and DBA.Prod):
System catalog ($SYSTEM.SQL) Owner = 001,255
Security = "OOOO"
$SYSTEM.SQL.CATALOGS Owner = 001,255
Security = "GGOO"
This example shows catalog security that gives any network user remote read access.
Any user in the database administrator’s user group can create catalogs on this
system, either locally or remotely.
System catalog ($SYSTEM.SQL) Owner = 001,255
Security = "OOOO"
$SYSTEM.SQL.CATALOGS Owner = 001,255
Security = "NCOO"
Creating Base Tables
Base tables are the foundation of an SQL/MP database. All data physically resides in
the base tables. When you create a table with the CREATE TABLE statement, you
specify the definition of each data column and the attributes of the physical file in which
the table is to be stored. Carefully consider the file attributes to ensure that the table
will meet the needs of your application.
The CREATE TABLE statement stores the table definition in the specified SQL catalog
and creates the table, which physically exists as a disk file. Before creating a table, you
should understand the three types of table organizations and column, key, and index
design considerations. For more information, see Understanding SQL File Structures
on page 3-1.