Neoview Workload Management Services Guide (R2.5)

For information on connection rules, see “Connection Rules” (page 70).
After the client application connects to the Neoview platform and is assigned to a service, WMS
proceeds with the “Compilation Phase” (page 24).
Compilation Phase
After a query is prepared, the NDCS server passes the execution decision making to WMS. WMS
compares the compiler estimates of the query against the compilation rules set for the service
and, along with other criteria, determines whether to permit the query to start executing. Figure 1-3
(page 24) shows the sequence of events (designated by the numbers in the diagram) that occur
when compilation rules are applied during the compilation phase.
NOTE: If query statistics aggregation is enabled for the service, WMS ignores the compilation
rules and proceeds with checking the maximum CPU busy and maximum memory usage.
Figure 1-3 How Compilation Rules Are Applied
1
3
2
vst112.vsd
Neoview Data Warehousing Platform
Neoview
Database
Runtime
Statistics
(RMS)
NDCS Server
Neoview
WMS
Client Application
Issuing a Query
Management Tool for
Monitoring WMS
1. The client application submits a query to the NDCS server.
2. The NDCS server sends compiler estimates of the query requesting permission to execute
to WMS.
3. WMS compares the compiler estimates with the compilation rules set for the service and,
along with other criteria, determines whether to permit the query to start executing.
If there are no compilation rules in effect for the service or if none of the conditions of the
compilation rules is met or if query statistics aggregation is enabled for the service, WMS
checks if there are sufficient resources to execute the query. When there are sufficient system
resources, a query can enter into execution directly or from the WAITING state. If a query
is in the HOLDING state, you must manually release the query to allow it to start executing.
Figure 1-4 (page 25) shows how WMS handles an incoming query.
24 Introduction