Understanding SYSSQL System Catalog Views [ HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL ] MPE/iX 5.0 Documentation
HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL
Understanding SYSSQL System Catalog Views
Most application software tools on the PC use a special set of views to
access system catalog information on the database server. These system
catalog views, owned by SYSSQL, are intended to be a common subset of
system catalog views supported by most SQL DBMSs.
For more information about these special views, refer to the Gupta
manual, SQLBase SQLTalk Language Reference Manual. For information about
the differences between ALLBASE/SQL and the SYSSQL views, refer to the
section "SQL Differences Between ALLBASE/SQL and SQLBase" later in this
chapter. For information about ALLBASE/SQL system catalog tables, refer
to the ALLBASE/SQL Database Administration Guide.
The views owned by SYSSQL were installed when you executed the Views
Script from the Scriptor dialog box.
Editing the VIEWS.SCP File
If your SQL.INI file contains all the valid DBEnvironments and
ALLBASE/SQL users, you can change just the database code and/or the user
code in the VIEWS.SCP file. These codes will then reference the codes in
the SQL.INI file.
Change the database code from server1 to the new name, and if necessary,
change the sysadm user code to the new name. Then execute the Views
Script from Scriptor as described earlier in this chapter.
ISQL and SYSSQL Views
The SYSSQL views can be installed on the database server two ways:
* From the PC client, using the Views Script with Scriptor.
* From the database server, using VIEWS.SQL with Interactive
Structured Query Language (ISQL).
The second mBethod is discussed here. The PC API product includes
scripts called VIEWS.SQL and UNVIEWS.SQL that you can use to add and
remove the SYSSQL views. To use the .SQL scripts in ISQL, follow these
steps:
* Upload the VIEWS.SQL and UNVIEWS.SQL files to the database server
(The extensions to the scripts are then automatically dropped.
These files will be used as command files in ISQL.)
* Type ISQL at the operating system prompt.
* Connect to the DBEnvironment from the ISQL prompt:
isql=> CONNECT TO 'DBEName';
* Install the SYSSQL views:
isql=> START VIEWS;
Do not use VIEWS.SCP on a DBEnvironment with an earlier version of SYSSQL
views. Refer to the section "Migrating to PC API" earlier in this
chapter.
MPE/iX 5.0 Documentation