SQL Server Alert System: 'Fatal Error Current Process

Ashwan 521 Reputation points
2021-03-07T23:40:41.627+00:00

Hi

Currently I configured event alerts though SQL agent severity 025 fatal error" to email DBA group . Every day network security process is running and that will kicked off SQL agent severity 025 fatal error" to email DBA group . this is bit of pain . So how to exclude this process to kick off this even email. SQL Server identify the network security process as "025 fatal error"

This is happening in all SQL envs

Any idea please

thanks

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,653 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. CathyJi-MSFT 21,081 Reputation points Microsoft Vendor
    2021-03-08T02:57:21.567+00:00

    Hi @Ashwan ,

    Did you mean network security process will trigger the SQL alter and sent the email notification to DBA email group? How did you define the SQL Server Alert? What will trigger the alter that you defined? Did you get any useful information from SQL error log?

    Severity 25 Errors--- A severity 25 error is a fatal system error. I have heard that severity 25 is more or less a catch-all for miscellaneous fatal errors. I have only seen this error when related to failed upgrades: something prevents one of the upgrade scripts from running, and a severity 25 error is thrown. Quote from this blog Dealing with high severity errors in SQL Server.

    0 comments No comments

  2. tibor_karaszi@hotmail.com 4,301 Reputation points
    2021-03-08T13:19:43.333+00:00

    You can't specify what you want an alert for all error in a certain severity level, and then exclude specific messages within that severity level. (A long long time we could do that by entering those error numbers in a specific place in the registry, but that is long gone).

    I would make sure that this doesn't happen, in the first place. Why do the SQL Server throw that security, and reconfigure whatever is triggering it so it doesn't happen anymore. 25 is the most sever severity level!

    If above, for some reason isn't an option, when either remove the alterint for severity level 25, or specify a rule in your mail system to disregard these emails.

    0 comments No comments