SQL/MX 3.2.1 Reference Manual (H06.26+, J06.15+)

Introduction
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-004
1-20
Concurrency
If you restore with PARTONLY (only one or more partitions are restored) or if you
restore the entire partition (that is, the partition did not exist in the target table before
restore), the redefinition time stamp of the table is updated.
If only data is restored (the partition existed in the target table before the restore), the
last open timestamp of partition data fork is updated, and the data modification
timestamp of the partition data fork is updated.
Table 1-5 lists concurrency limits on utilities.
PURGEDATA Yes
RESTORE Yes**
REVOKE No
UPDATE STATISTICS No
VERIFY No
* Manual recompilation might be required.
** If you restore an entire table (including metadata), all timestamps are updated. The table needs to be dropped
and re-created.
Table 1-5. Concurrency Limits on Utility Operations (page1of3)
Utility DML operations Other utilities
DDL
operations
Utilities that only read
metadata information:
EXPORTDDL
INFO
MXGNAMES
SHOWDDL
SHOWLABEL
VERIFY
All DML operations
(SELECT, UPDATE,
DELETE, INSERT) can be
performed concurrently.
Any utility in this
category can be
performed
concurrently.
Not
recommended.
Utilities that read both
metadata and user
data:
BACKUP
FASTCOPY (source
table only)
DUP (source table
only)
Only SELECT is allowed. Utilities that read
metadata can be
performed only
concurrently.
Not
recommended.
Table 1-4. Operations Effect on Table Timestamps (page 2 of 2)
Alter Operation Timestamp Updated