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-13
Views
For more information about SQL/MX indexes, see the SQL/MX Reference Manual.
Views
In NonStop SQL/MX, use the SQL/MX CREATE VIEW statement to create ANSI views,
which have three-part ANSI names instead of Guardian physical names. The
distinction between SQL/MP protection and shorthand views does not exist in NonStop
SQL/MX. If an SQL/MX view is based on a single table, the view can be read, and
usually the view can be updated provided that the view meets certain criteria. If an
SQL/MX view is based on multiple tables or other views, it can be read but not
updated. For more information about updatable and non-updatable views, see the
SQL/MX Reference Manual.
To create an SQL/MX view, you must have SELECT privileges for the database objects
underlying the view. In SQL/MX view definitions, you can use a UNION operator,
whereas you cannot in NonStop SQL/MP. You cannot refer to SQL/MP objects in
SQL/MX view definitions. The ALTER VIEW statement does not exist in NonStop
SQL/MX. To alter an SQL/MX view, you must use the DROP VIEW and CREATE VIEW
statements, respectively, to drop and then re-create the view.
NonStop SQL/MX handles security on views differently than NonStop SQL/MP. In
NonStop SQL/MP, you must have appropriate security on the underlying table of the
Table 11-4. Index Table Attributes in NonStop SQL/MP and NonStop SQL/MX
SQL/MP Attributes Supported in SQL/MX?
ALLOCATE Yes
AUDITCOMPRESS Yes
BLOCKSIZE Yes (only 4096)
BUFFERED No
CLEARONPURGE Yes
DCOMPRESS No
EXTENT Yes
FORMAT No (SQL/MX tables are always format 2.)
ICOMPRESS No
ISLACK No
LOCKLENGTH No
MAXEXTENTS Yes
NOPURGEUNTIL No
SERIALWRITES No
SLACK No
TABLECODE No
VERIFIEDWRITES No