Database Performance Analyzer consists of:
- A DPA server
- A DPA repository database
- One or more database instances you want to monitor
The DPA server collects performance data from a set of database instances you choose to monitor. DPA stores this data in the repository database, and makes it available to users through its web-based interface.
For optimal performance, the DPA server, repository database, and the monitored database instances must reside on the same high-speed LAN. If your environment contains database instances that are on separate LANs, SolarWinds recommends creating a repository database on each LAN. For cloud monitoring, SolarWinds recommends deployment to the same region.
SolarWinds recommends installing one DPA instance on a computer. If you must install multiple instances on the same computer, submit a support ticket.
Key functions of the DPA server
The DPA server:
- Collects data from the monitored database instances and stores the data in the repository database.
- Provides a web-based interface that displays performance data from any computer with access to the DPA server. From this interface, you can monitor database activity, investigate performance issues, and configure alerts and reports.
Agentless monitoring for database instances and virtual environments
DPA remotely connects to each database instance using Java Database Connectivity (JDBC). DPA causes less than 1% overhead on the instance. No software is installed on the monitored server.
In a virtual environment, DPA can remotely connect to each VMware vCenter Server, ESX, or ESXi host. DPA causes less than 1% overhead on the monitored systems. No software is installed in the vCenter Server, ESX or ESXi host, or virtual machines.
DPA runs a query (the "quickpoll" query) on monitored database instances to collect information about wait events. By default, the quickpoll query runs once per second.