SQL/MP Installation and Management Guide

The SQL/MP Database Management Environment
HP NonStop SQL/MP Installation and Management Guide—523353-004
1-9
Database Management Operating Environments
and row redistribution with concurrent read and update capability available for the
table or index
•
Parallel table loads (using multiple SQLCI LOAD PARTONLY operations) and
index loads (using CREATE INDEX or LOAD command with PARALLEL
EXECUTION ON) to reduce the time required to load the object
•
Automatic recompilation or partial recompilation, which eliminates the need to
terminate program execution when changes in database structure or the
environment make rebinding necessary
•
Ability to defer name resolution in SQL statements until execution time
Database Management Operating
Environments
SQL/MP is accessible to the Open System Services (OSS) and Guardian operating
environments, as follows:
•
SQL/MP data is accessible to programs that run in the OSS and Guardian
environments.
•
SQL tables, views, indexes, collations, catalogs, and SQL programs that are stored
in Guardian files are manipulated by using SQLCI or Guardian utilities as
described in this manual.
•
SQL programs that are stored in OSS files are manipulated by using OSS utilities
as described in the Open System Services Shell and Utilities Reference Manual.
•
There are two SQL compiler interfaces, one for the OSS environment and one for
the Guardian environment:
°
c89 is used in the OSS environment, supports OSS path names as input files,
and produces OSS object files. For more information, see the SQL/MP
Programming Manual for C.
°
SQLCOMP is used in the Guardian environment, supports Guardian file names
as input files, and produces Guardian object files. For more information, see
the SQL/MP programming manuals.
•
The unique ZYQ name associated with an OSS path name can be used in some
Guardian and SQLCI utilities. There is only one ZYQ name for each SQL program
stored in the OSS environment, even if there are multiple links to the file.
•
Guardian file names can be accessed from OSS—and supplied as input to c89—
by using this format:
/G/volume/subvolume/file
•
An example of a file name follows:
/G/data1/subvol1/testfl