SQL Server IO error 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 IO Error 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 IO Error 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: IO error (incorrect checksum) occurred when reading a data file. The read eventually completed successfully but encountered a checksum error. Check the device for other errors. Mini DBA evaluates this alert once a minute so changes are detected quickly.

How this alert helps

This alert reports a checksum or read-path I/O error. Even when a later read succeeds, the event can indicate storage, controller, driver, memory, or data-page integrity problems that require prompt investigation.

When to enable it

Enable it on every production SQL Server instance. Treat it as an integrity and storage warning rather than a normal workload threshold.

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

Preserve the SQL Server error details, identify the affected database, file, page, and device, and check the SQL Server, Windows, and storage-platform logs for related errors. Run the organization's approved integrity checks, validate backups, and escalate suspected corruption or hardware faults; query tuning is not a remedy for a checksum error.

Investigation workflow

Record the exact SQL Server error, timestamp, database, file, page, and device reported.
Correlate it with SQL Server error-log entries, operating-system events, storage alerts, and recent infrastructure changes.
Run approved database integrity checks and verify that a usable backup and restore path exists.
Follow the corruption or storage-incident runbook and confirm that no further I/O errors occur.

Avoiding alert noise

Do not suppress repeated checksum or I/O errors as ordinary noise. Deduplicate identical events for notification routing if necessary, but keep the underlying incidents visible until storage and database integrity have been verified.