SQL/MP to SQL/MX Database and Application Migration Guide

Converting SQL/MP Tables to SQL/MX Tables
HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001
5-4
Differences Between SQL/MP and SQL/MX
Databases
Unlike NonStop SQL/MP, which supports limited parallel updates, NonStop SQL/MX
does not currently perform partition-label updates in parallel.
Character Sets and Collations
NonStop SQL/MX does not currently support all the character sets that NonStop
SQL/MP supports, such as Big5 and ISO88592 through ISO88599. NonStop SQL/MX
supports only the DEFAULT collation in a SQL/MX table. For more information about
supported character sets in NonStop SQL/MX, see the
SQL/MX Reference Manual.
Load Capability in NonStop SQL/MX
In NonStop SQL/MP, you can use the SQLCI LOAD command to load data from a
SQL/MP table or a Guardian file into another SQL/MP table or its indexes. NonStop
SQL/MX has no equivalent command for loading data from a SQL/MX table or a
Guardian file into another SQL/MX table or its indexes. The SQL/MX
import utility
moves data from an input file in ASCII or UCS2 format or from a process such as
DataLoader/MX into an existing SQL/MX table. For more information about
import,
see the
SQL/MX Reference Manual and SQL/MX Installation and Management Guide.
Differences Between SQL/MP and SQL/MX
Databases
Many features of a SQL/MX database are similar to the features of a SQL/MP
database, such as the features required for distributed databases, database protection
and recovery, data integrity, database security, parallel processing, and high
availability. However, some differences exist between SQL/MP and SQL/MX databases
for the following entities:

System Catalogs and Metadata on page 5-5

User Catalogs and Schemas on page 5-5

Database Object Names on page 5-6

Distributed Database Objects on page 5-7

Database Object Security on page 5-7

Tables on page 5-8

Partitions on page 5-11

Indexes on page 5-11

Views on page 5-13

Collations on page 5-13