ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-47
Configuring NonStop ODBC Server Catalogs
a database at a datasource can specify as default any database within that
datasource.
As the database administrator you must choose which SQL/MP data objects should be
exposed to ODBC clients. The administrator must also determine whether complete
SQL/MP catalogs should be customized or whether virtual databases should be
constructed, exposing only a selected subset of SQL/MP data.
Listed below are ways in which you might customize your data:
•
For each independent collection of configuration data desired, create a NonStop
ODBC system catalog. For each collection that is not based on the SQL/MP
system catalog, set the DEFINE =_NSODBC_SYSTEM_CATALOG and perform
NOSCOM SYSCAT INSTALL. This step is usually performed for the primary ODBC
configuration within NOSINST and is indicated for each additional collection of
desired configuration data. It is also possible to use NOSINST to perform this step
and populate the catalog with default administrator configuration values.
•
For each complete SQL/MP catalog that is to be exposed, perform NOSCOM
USERCAT INSTALL on the SQL/MP catalog subvolume. This function must be
done for each NonStop ODBC system catalog for which access to SQL/MP data is
desired.
•
For each virtual database, create an independent ODBC user catalog, again using
NOSCOM USERCAT INSTALL on an empty subvolume. Then perform the
NOSCOM functions ADD TABLE, ADD INDEX, and ADD VIEW for each virtual
object reference. Even though an index is not directly accessible by a user, you
need to add a mapping entry so that applications can better choose access path
and join actions. As with the preceding step, this virtual database must be added
to each NonStop ODBC system catalog for which access to this collection of
SQL/MP data is desired.
•
As the database administrator, you can customize (or de customize) other SQL/MP
catalogs at any time, as follows:
NOSCOM> USERCAT INSTALL Guardian-subvolume
Guardian-subvolume is a file-system subvolume name such as $DATA.MINE.
This subvolume can be an existing or new SQL/MP catalog. If the catalog does not
yet exist, then a SQL/MP catalog is created before the NonStop ODBC system
Note. N SQL/MP and its underlying file system perform the actual access authorization. The
registry list of SQL/MP objects mapped for ODBC access provides a mechanism for
customizing access to an application’s specific needs for performance and usability. Even if a
SQL/MP object is registered in an ODBC database, the user might not have access rights on
that object.
Note. The metadata created and stored in the NonStop ODBC catalog tables is loaded
only at the time the catalog is first created and populated by USERCAT INSTALL.
USERCAT INSTALL of a SQL/MP catalog that already has a completed set of ODBC
catalog tables requires only registry in the designated ZNSDB system table.