ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-46
Configuring NonStop ODBC Server Catalogs
If, in Figure 2-2, User A had decided that the profile change from P1 to P2 should not
be propagated to all running servers, User A would not have chosen to update the
system configuration timestamp; when User A reconnected at time T4, the server
would have continued to use the old profile. If a new server were started after the
profile change from P1 to P2, however, the new server would have adopted the new
profile definition immediately, because it had not been running under the old profile.
Configuring NonStop ODBC Server Catalogs
SQL/MP data is accessible to NonStop ODBC Server users as collections of objects at
a named datasource. A datasource is defined by the Network Service Name to which a
user connects and by the collection of data groupings available to a user connected to
that service. These groupings of data are known as databases. A user connecting to a
datasource can specify a specific database or use the default database for that
datasource.
An ODBC database contains a collection of accessible objects, referred to in ODBC as
ACCESSIBLE_TABLES. In NonStop ODBC Release 1, and by default in Release 2, an
ODBC database and a SQL/MP catalog are equivalent collections of accessible
objects. The INSTALL process registers each SQL/MP object into the mapping tables.
NonStop ODBC Release 2 Features
NonStop ODBC Release 2 includes a set of features that can be used to customize the
ACCESSIBLE_TABLES list to match client application needs. First, you can create a
NonStop ODBC catalog independent of the SQL/MP data that will be made available
for access by using the ADD {TABLE | VIEW | INDEX} commands. You can modify
NonStop ODBC catalog configurations for the access rights and application needs of
clients connecting and using SQL/MP data, without redesigning the SQL/MP catalog.
SQL/MP data can be customized for access in more than one ODBC system.
A major benefit of creating these virtual databases is the performance gain at connect
time, when most applications download all of the metadata in that catalog to the PC
platform. SQL/MP catalogs easily grow to a size where the download of metadata
exceeds both the space available on the PC and a reasonable time frame for
completing the connect operation.
Another NonStop ODBC Release 2 feature is the ability to install more than one
NonStop ODBC system catalog on a system. Each ODBC system catalog is a
complete, independent collection of ODBC configuration data and ODBC-customized
SQL/MP data grouped into reference groups, or databases. A user that can connect to
Note. Applications often have the restriction of accessing data from only one database. This
can be solved by using the virtual database mechanism to reference objects across multiple
SQL/MP catalogs.