Neoview Workload Management Services Guide (R2.5)

1 Introduction
This chapter introduces the Neoview Workload Management Services (WMS) and describes its
purpose and benefits, how it works, and how to start using it.
• “Purpose and Benefits of WMS” (page 21)
• “How WMS Manages Queries” (page 21)
• “How WMS Applies Rules and Services” (page 22)
• “Query Statistics Aggregation” (page 27)
• “How to Start Using WMS” (page 30)
Purpose and Benefits of WMS
The Neoview Workload Management Services (WMS) feature provides the infrastructure to help
you manage query workloads and system resources in the mixed workload environment of a
Neoview platform.
In the mixed workload environment of an enterprise data warehouse, like the Neoview platform,
a variety of query workloads must run smoothly without interruptions to their throughput and
performance. As a database administrator, you need to be able to control when different types
of queries enter the system and how they proceed to execute, and you need to ensure that system
resources remain available for query execution. You do not want a rogue query to monopolize
system resources and slow down or prevent other queries from running in the system.
Using WMS, you can influence when queries run and how many system resources they are
allowed to consume by assigning groups of queries (that is, query workloads) to WMS services.
You can create your own services in WMS and configure them to have a relative priority and a
set of thresholds for the execution environment. That way, you can maintain different query
workloads and ensure that enough system resources are available to higher priority workloads
while minimizing contention with lower priority workloads.
In addition to the priority and thresholds that you define for each service, you can create rules
and associate them with one or more services. The rules that you associate with services cause
WMS to perform an action or a set of actions on queries in a session if certain conditions are met.
WMS supports these types of rules:
• Connection rules, which are applied when a client session connects to the Neoview platform
and which determine the service to assign to the client session and any runtime settings
• Compilation rules, which are applied after a query is compiled (that is, prepared) and which
determine whether the query starts to execute, is put on hold, or is rejected, preventing
queries that will use too many system resources or will take too long to run from executing
• Execution rules, which are applied after a query has been executing and which determine
whether the query should continue executing or be cancelled if the query is consuming too
many system resources or is taking too long to run
In addition to automating workload management by implementing services and rules in WMS,
you can also monitor queries in services in real time to identify problematic queries, and you
can manually hold or cancel queries to prevent them from monopolizing system resources.
How WMS Manages Queries
WMS acts as a query manager for Neoview Database Connectivity Service (NDCS) server
processes, obtaining information from the requesting NDCS servers and using that information
to manage query workloads. WMS monitors queries that are submitted to NDCS servers from
various client applications, such as JDBC, ODBC, .NET client applications, or the NCI
command-line interface. WMS manages all Data Manipulation Language (DML) queries, such
as INSERT, UPDATE, DELETE, and SELECT statements, which are either prepared and executed
or executed directly.
Purpose and Benefits of WMS 21