|
IBM DB2 Warehouse features a set of extreme workload management capabilities that can enable real-time delivery of business insights while continuing to support all of your traditional needs for information access, analysis and reporting through a single data warehouse environment—without compromising performance. With traditional data server solutions, it’s difficult to deliver information in real time to a broad set of users and applications because more users running queries simultaneously puts a technological strain on the underlying infrastructure. In addition, large batch oriented data loading or reporting jobs and highly analytical processes driven by strategic and tactical planning efforts could have an impact on requests coming from users that are interacting with a customer or other processes requiring immediate response times. With the advanced workload management capabilities now available in DB2 Warehouse, however, you can not only prioritize queries coming from different users and applications, but you can even control the amount of underlying resources dedicated to those processes, helping to ensure that service level agreements for key departments, customers and users are met while continuing to support traditional business intelligence needs. DB2 Warehouse provides SQL query performance management and monitoring tools to more effectively control the workload of the warehouse. The DB2 Warehouse Design Studio supports the ongoing development, refinement, validation, and monitoring of a workload management solution called a workload management scheme. You can use the Design Studio to define the collection of entities that make up a workload management scheme. You also create the limits that control database activities.
Features:
- Database service classes: All of the work for a database is executed in the database service classes that you define. Use the superclasses and subclasses in your database service class hierarchy as the primary points where you can allocate system resources, apply controls on database work, and monitor database work.
- Operating system service classes: If you run the database on AIX®, use operating system service classes to control resource usage for database-related work that is performed in the operating system.
- Work identities: Use database connection attributes to specify the primary sources and submitters of work by creating work identities. Then, you can associate the work identities with the service classes where the work is executed. You also use work identities to enforce controls on the sources of work.
- Work type sets and work types: Classify the database work into sets of work types, such as DML, DDL, Read, Write, and so on. Then, map the work types to the database subclasses that execute the work.
- Histogram templates: Create custom templates for the histograms that display your monitoring data, or use the default templates.
Benefits
- Route database activities to stable and predictable execution environments. Enforce boundaries for these activities.
- Control the distribution and use of system resources. Set limits for consumption of system resources, prevent misuse of resources, and track usage patterns.
- Control individual database activities such as poorly written queries, and database activities that run concurrently and over-consume resources.
- Enforce control over database work at different levels. Establish boundaries that operate on only the database activities that occur within the associated entity: the entire database, a service class, a work identity, or a work type. Specify whether the activities that exceed the boundaries are queued, stopped, or allowed to execute.
| 
