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-8
Tables
SQL/MX applications are always stored in the OSS environment. For more information
about OSS security, see the
OSS User’s Guide. For more information about securing
SQL/MX user modules, see the
SQL/MX Installation and Management Guide.
Tables
An SQL/MX table is described in an SQL/MX schema yet stored in one or more
physical files in the Guardian environment. Unlike SQL/MP tables, which have
Guardian physical names, an SQL/MX table has an ANSI name of
catalog.schema.table, where catalog is the name of the catalog, schema is the
name of the schema, and
table is the name of the table. SQL/MX tables also differ
from SQL/MP tables in these ways:
•
Physical File Organization on page 11-8
•
File Attributes on page 11-8
•
Audited Tables Only on page 11-9
•
Column Names on page 11-9
•
Column Data Types on page 11-10
•
Primary Keys on page 11-10
•
Clustering Keys on page 11-10
•
Constraints on page 11-11
Physical File Organization
SQL/MP tables can be relative, entry-sequenced, or key-sequenced tables. However,
SQL/MX tables can be only key-sequenced tables.
File Attributes
In SQL/MX tables, you can set some of the SQL/MP file attributes, as Table 11-1
shows.
Table 11-1. File Attributes in NonStop SQL/MP and NonStop
SQL/MX (page 1 of 2)
SQL/MP Attributes Supported in SQL/MX?
ALLOCATE Yes
AUDIT No
AUDITCOMPRESS Yes
BLOCKSIZE Yes (only 4096)
BUFFERED No
CLEARONPURGE Yes