Page 185 - DCAP508_DATABASE_ADMINISTRATION

Deepak Mehta, Lovely Professional University
Unit 13: Monitoring Database Modifications

Unit 13: Monitoring Database Modifications Notes

CONTENTS
Objectives

Introduction
13.1 Defining DAM
13.2 Market Drivers
13.3 Use Cases

13.4 Common Use Cases for DAM
13.5 Common DAM architectures
13.6 User Benefits
13.7 Summary

13.8 Keywords
13.9 Review Questions
13.10 Further Readings

Objectives

After studying this unit, you will be able to:

Understand the meaning of Database Activity Monitoring
Learn about common use cases for DAM
Know about common DAM architectures

Analyze the various market forces driving DAM tool deployment
Introduction

Continuous monitoring of the system, network, database operations, application, and other
system components, ensures early detection of problems. Early detection improves the user’s
system experience because problems can be resolved faster. In addition, monitoring captures
system metrics to indicate trends in system performance growth and recurring problems. This
information can facilitate prevention, enforce security policies, and manage job processing. For
the database server, a sound monitoring system must measure availability and detect events
that can cause the database server to become unavailable, and provide immediate notification to
responsible parties for critical failures.
The monitoring system itself must be highly available and adhere to the same operational best
practices and availability practices as the resources it monitors. Failure of the monitoring system
leaves all monitored systems unable to capture diagnostic data or alert the administrator of
problems.

13.1 Defining DAM

Database Activity Monitors capture and record, at a minimum, all Structured Query Language
(SQL) activity in real time or near real time, including database administrator activity, across

LOVELY PROFESSIONAL UNIVERSITY 179