ODBC Server Installation and Management Manual

Managing NonStop ODBC Server Resources
HP NonStop ODBC Server Installation and Management Manual—429395-002
5-10
Usage Considerations
SQL_FETCH statements. The second set is for the DELETE statement, and the third
set is for the UPDATE statement.
The driver translates ODBC functions that retrieve catalog information, such as
SQLColumns, and TSQL functions such as DBNAME, to SQL/MP SELECT
statements; resource use for execution of such SELECT statements is collected also.
For a DDL statement, only the NonStop ODBC Server process time is collected,
because in SQL/MP the process time returned by SQL Executor does not include the
Catalog Manager's process time. No resource statistics are being gathered by the
Catalog Manager.
Managing the Resource Accounting Configuration
A full set of utility statements is available to create a resource accounting log table and
to set up and change the accounting profiles. Dynamic reconfiguration and managing
of the resource accounting table is also provided.
Only the database administrator (a member of the super group) has the authority to
establish and change the resource accounting configurations. This restriction is
because the data is used by the database administrator to perform administrator
functions such as chargeback to client departments and monitoring system use.
No SET command is allowed to alter the accounting configurations. The reason is that
the SET command is issued by each user to change the run-time behavior; and the
individual user does not have the authority to change the accounting configuration set
up by the database administrator.
Managing the Resource Accounting Table
Only the database administrator has the authority to create or delete a resource
accounting log table.
Managing Resource Accounting Data
A resource accounting log table must have sufficient space to accommodate the
amount of data being collected, especially the data for each SQL statement. When the
table becomes full, a message is written to $0, and resource accounting is disabled. It
is the responsibility of the client and the database administrator to determine whether
to continue—with the collection of resource accounting data suspended—or to free up
enough space to resume data collection.
In an overflow situation, the database administrator could choose to perform following:
•
Alter the MAXEXTENT size of the accounting log table (if it is below the maximum
limit).
•
Create a new accounting log table in a different location and change all user
profiles to point to the new table.
•
Purge data from the existing table (if the report has been generated) and continue.