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 Guide540435-005
11-2
ANSI Compliance
Before converting an SQL/MP database object to NonStop SQL/MX, be aware of the
Reasons for Keeping SQL/MP Tables
on page 11-3.
ANSI Compliance
NonStop SQL/MX is open, portable, and, most importantly, uses an industry standard:
the American National Standards Institute (ANSI) version of SQL. SQL/MX Release 2.x
is based on ANSI SQL:1999 and includes support for features from higher levels of the
standard.
SQL/MX Release 2.x supports the creation of ANSI-compliant catalogs, schemas, and
database objects. SQL/MX Release 2.x uses three-part ANSI names, consisting of the
catalog, schema, and object name, to refer to database objects:
catalog.schema.object
SQL/MX views are ANSI compliant and offer these advantages:
No view text limit
Aggregations and unions specified in view text (aggregate over a view or joined to
another table)
Updatable
Security model that does not require users to have privileges on the underlying
tables unlike NonStop SQL/MP
For details about how SQL/MX features comply with ANSI standards, see the
SQL/MX
Reference Manual.
New Functionality in NonStop SQL/MX
NonStop SQL/MX has useful functionality for database objects that NonStop SQL/MP
does not have. This functionality includes:
Triggers
Referential integrity constraints
Hash partitioning
Unicode character set
For more information, see the
SQL/MX Reference Manual.
Enabling SQL/MX Applications to Access Specific Tables
If you are using NonStop SQL/MX to query SQL/MP tables, you might need to convert
an SQL/MP table to an SQL/MX table. Your application might require functionality that
is not supported in NonStop SQL/MP, or the application might need to access data in
an SQL/MP table that NonStop SQL/MX cannot access. For example, NonStop
SQL/MX cannot query relative tables or entry-sequenced tables that are partitioned. If