如何抑制Error:9245（Severity:16）查询通知错误告警？
Got it, let's tackle those pesky Error 9245 notifications you're getting nonstop. I totally get the frustration—you’ve got Severity 16 errors set up to alert automatically, but this specific alert is just noise that doesn’t need your immediate attention. Here are the most straightforward ways to suppress these alerts without breaking your existing critical error monitoring:
1. Filter Out Error 9245 in Your SQL Server Agent Alert
If you’re using SQL Server Agent to trigger your Severity 16 alerts, you can tweak the existing alert to exclude this exact error:
- Open SQL Server Management Studio (SSMS), head to SQL Server Agent > Alerts.
- Find your Severity 16 alert, right-click it and select Properties.
- In the General tab, where you’ve set the severity level to 16, look for the filter options (usually labeled "Message text" or "Filter").
- Add a condition that says Error Number NOT EQUAL TO 9245. This way, the alert will still fire for all other Severity 16 errors, but skip this one entirely.
2. Stop Error 9245 from Being Logged (Permanent Fix for Log-Based Monitoring)
If your monitoring tool pulls alerts directly from the SQL Server error log, you can disable logging for this error altogether:
- Run this T-SQL command in SSMS:
sp_altermessage 9245, 'WITH_LOG', 'false';
- To double-check the change worked, run:
SELECT message_id, is_event_logged FROM sys.messages WHERE message_id = 9245;
This will prevent Error 9245 from showing up in the error log at all, so your monitoring tool won’t pick it up. Just make sure you’re okay with never seeing this error logged—since it’s only about suppressed query notification errors, this is usually safe for most environments.
3. Add an Exception in Your Third-Party Monitoring Tool
If you’re using a tool like SolarWinds, Datadog, or New Relic for monitoring, you can adjust the alert rule to exclude Error 9245:
- Locate the rule that triggers alerts for Severity 16 errors.
- Add a filter to exclude any alert where the error number is 9245.
- Save the rule changes, and you’ll stop getting notifications for this specific error while keeping your critical Severity 16 alerts intact.
Quick Notes to Keep in Mind:
- Before making any changes, just confirm you don’t rely on query notifications in your environment—Error 9245 is only about suppressed errors for that feature, so it’s almost always harmless to ignore.
- If you ever need to re-enable logging or alerts for Error 9245 later, run
sp_altermessage 9245, 'WITH_LOG', 'true';to restore logging, or adjust your alert/monitoring rules back to their original state.
内容的提问来源于stack exchange，提问作者MyDoggieJessie
