ODBC Server Installation and Management Manual

Managing NonStop ODBC Server Resources
HP NonStop ODBC Server Installation and Management Manual—429395-002
5-13
Defining Policies
the individual user). For small queries, the status information is not essential because
the time to execute such a query is not significant. By limiting the entries in the query
status table, you can eliminate unnecessary SQL writes and deletes to the query status
table.
During run time, the NonStop ODBC Server periodically checks whether a query has
exceeded its defined limits and initiates an appropriate action.
Figure 5-1 shows the relationships among the NonStop ODBC Server, the governing
policy table from which it obtains governing policies, and the query status table to
which it logs query status data, as well as the SQL/MP executor and the actions it
initiates based on information from the NonStop ODBC Server.
Defining Policies
Resource governing is controlled through the use of governing policies. A governing
policy defines a set of limits and the actions to be performed when a given limit is
exceeded. Three utility statements have been provided for maintaining these policies:
ADD, MODIFY, and REMOVE GOVERNING. Resource governing is enabled or
disabled through the user profile. A single policy can be established for all users or
different policies established for individual users.
Figure 5-1. Resource Governing Facility Architecture
NonStop
ODBC
Server
NonStop SQL/MP
Executor
Query StatusTable
(transient)
Client Information
Session Information
User Information
Profile Information
Statement Text
and so on
Limit
Action
Scheduling and
Governing Policy
SCS
Result Sets and/or
Warning Messages
Sent to Client
Triggered
Actions
ESP ESP
VST025.vsd