Database Performance History

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Mini DBA Engine collects database monitoring evidence continuously so you can investigate a performance incident after the live symptoms have disappeared. Historical views keep the selected Engine, server and time range in context while you move between metrics, queries, waits, alerts and platform-specific diagnostics.

Mini DBA database estate and performance history

When To Use Performance History

Users report a slowdown after the affected sessions or queries have completed.
An alert needs enough context to explain what the database was doing at the time.
A recurring problem needs to be compared across several incidents.
You need a normal baseline before changing a query, index, configuration or capacity.
A service review or engineering handover needs evidence rather than a current-status snapshot.

Historical Evidence Available

The exact views depend on the database platform and enabled monitoring features. Historical investigation can include:

Server, database and host performance metrics.
Query duration, executions, CPU, reads, writes and available execution plans.
Wait activity, sessions, blocking and deadlock evidence.
Active and historical alerts from trial or licensed Engines.
Database files, storage, connections and platform-specific health indicators.

Community Edition: metric and query history remains available where supported, but Community Engines do not evaluate, retain or expose alerts. See Licensing for the complete entitlement rules.

Reconstruct An Incident

Select the Engine and monitored server affected by the incident.
Open a relevant historical view and narrow the time range to the reported period.
Find the first signal that changed instead of assuming the largest graph is the cause.
Compare workload evidence with waits, blocking, alerts and resource metrics over the same interval.
Open the responsible query, plan, deadlock or platform detail where available.
Compare the incident with a normal period and record the evidence supporting the conclusion.

Use AI And MCP With History

The AI Assistant can optionally receive relevant page context and the selected evidence to explain a historical symptom or suggest the next checks. The MCP Server lets an approved AI client ask broader questions across live and historical monitoring tools, including multi-engine and managed-service workflows.

AI responses should guide investigation. Verify important conclusions in Mini DBA and follow normal review and change-control procedures before modifying production databases.