SQL/MX Comparison Guide for SQL/MP Users

Embedded SQL
HP NonStop SQL/MX Comparison Guide for SQL/MP Users—523735-003
4-14
Similarity Checks and Automatic Recompilation
Number of indexes - more indexes at
run time than at compile time
Yes No for INSERT,
UPDATE, DELETE
queries.
Yes for SELECT.
Number of indexes - fewer indexes at
run time than at compile time
Yes, if index is not used
by plan
No for INSERT,
UPDATE, delete
queries.
Yes, for SELECT, if
index is not used by
plan.
Unique index present both at compile
and run time
Yes No, fails for SELECT
Key tags (or values) for indexes Yes No
Creating and redefinition timestamp Yes Yes
Audit attribute Yes, with minor
exception
No
Any of these attributes: ALLOCATE,
AUDITCOMPRESS, BUFFERED,
CLEARONPURGE, EXTENT (primary
and secondary), LOCKLENGTH,
MAXEXTENTS, NOPURGEUNTIL,
OWNER, SECURE, SERIALWRITES,
TABLECODE, VERIFIEDWRITES
Yes Yes
Statistics on the table Yes Yes
Column headings Yes Yes
Catalog where table is registered Yes Yes, could be in
different schema
Number of columns - more columns at
run time that at compile time
Yes, with same
attributes and no
SELECT
No
VIEWs on the table Yes, only for qualifying
protection views
No
Check constraints, referential integrity
constraints, or triggers on the table
Yes. Ignores check
constraints
No
Difference between compile and run
time module
Does SQL/MP
similarity check pass?
Does SQL/MX
similarity check pass?