SQL Server full transaction log alert

Start Here

Manual Home Installation Windows Installation Linux Engine Container Linux Console Container 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

Legacy Documentation

The Full Transaction Log alert notifies you when its configured condition is met on SQL Server instances so you can investigate and respond.

Screenshot pending: Mini DBA SQL Server Full Transaction Log alert screenshot placeholder

Alert summary

Platform: SQL Server
Alert category: Disk
Default enabled: true
Default evaluation frequency: Minute

What Mini DBA checks

Mini DBA describes this alert as: The transaction log is full Mini DBA evaluates this alert once a minute so changes are detected quickly.

How this alert helps

This alert gives Mini DBA a focused signal for a condition that can affect SQL Server reliability, performance, or operational visibility. It helps the team move from a general problem report to a specific metric, threshold, and investigation path.

When to enable it

Enable it once the instance has a normal workload baseline. It is especially useful on busy OLTP, reporting, and integration systems where resource pressure can quickly become user-visible.

Threshold guidance

This alert is based on a state or event rather than a numeric threshold. Tune its schedule, scope, severity, and notification route so that the response matches the importance of the instance.

Remediation for an active alert

Free space by removing safe-to-delete files, expanding the volume or tablespace, moving growth-heavy objects, correcting retention settings, or shrinking only after a documented one-off event. For recovery-related areas, verify that backups and log shipping or archiving are healthy before deleting anything.

Investigation workflow

Confirm the alert is still active and note the first seen time, affected instance, and severity.
Review the affected disk, tablespace, log stream, backup job, retention setting, and recent growth pattern in Mini DBA before changing configuration or ending sessions.
Compare the current value with the normal baseline for the same time of day or maintenance window.
Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding alert noise

Storage alerts should usually stay enabled even on quiet systems because the impact of missing them is high. Tune warning thresholds to leave enough time for approval, provisioning, and validation, especially when storage changes are handled by another infrastructure team.