Neoview Workload Management Services Guide (R2.5)

3 Understanding Your Workload Environment
To implement WMS services and rules, you should have a good understanding of your workload
environment and the types of query workloads that run in your enterprise data warehouse. This
chapter provides guidelines for helping you identify and define the query workloads in your
database environment.
Identifying Query Workloads in an Enterprise Data Warehouse
Table 3-1 shows some typical query workloads that run in an enterprise data warehouse:
Table 3-1 Typical Query Workloads in an Enterprise Data Warehouse
DescriptionQuery Workload Type
Near real-time data loading, which requires indexes to be updated and queries
to be optimized
Continuous data loading
Batch loads of less volatile information, which tend to run overnight or during
off hours
Incremental and batch data loading
Large volume of critical reports, which are run daily and require SQL tuning,
index creation, storage partitioning, and optimization
Daily standard reports
Complex analytical queries of prebuilt online analytical processing (OLAP)
cubes and materialized views with aggregated data and dimensional drill
downs
Tactical business analytics
Random, unpredictable use of the data with queries that occur sporadically
and are not tuned
Ad-hoc queries
Tactical use of the data warehouse as a source of information for OLTP
applications, requiring high-priority queries that have very quick response
times
Analytics and Business Intelligence
(BI) functionality in OLTP
applications
The actual query workloads in your database environment might differ from this list depending
on your business objectives and requirements.
Defining the Query Workloads
Use the service level agreement (SLA) objectives for your enterprise data warehouse to establish
the criteria for defining the query workloads. An SLA is a formal agreement that sets expectations
between the system manager and the end users of an enterprise data warehouse and defines
objectives for availability and performance. For example, an SLA might require a batch job to
load sales data from the previous day by 7:00 a.m., or it might require a particular sales report
to run in less than five minutes.
When defining your query workloads, consider the criteria in Table 3-2 (page 44).
Identifying Query Workloads in an Enterprise Data Warehouse 43