Sql-server – Error: 9245, Severity: 16, State: 1. / “During the last time interval X query notification errors were suppressed”

errorssql server

We are receiving this notification several hundred times a day and while we're regularly checking notifications from Severity 16 errors, this isn't something we're really concerned about.

I've read the article and replies at Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed and while that's very informative, I'd like to know how can we suppress it?

We have an automated alert set up for severity 016 errors and we don't exact categorize this one as an "action items" yet are receiving hundreds of them daily.

Is there a way to suppress it?

Best Answer

It's the simple built-in alerts that you can configure in SQL Server i.e. (EXEC msdb.dbo.sp_add_alert @params) - it emails the DBA team when that error is captured.

Since this particular "cause" is not exactly threatening the health of the server I was wondering "other than a mailbox rule" if there was a way to "omit" these particular ones containing "notification errors were suppressed" - so basically that they're not sent at all.

Related Solutions

Sql-server – Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed

The error 9245 message appears to be directly connected to the 'The query notification dialog on conversation handle...' message in that SQL Server 2012 SP1 appears to only show that error a maximum of 10 times (with the same timestamp) in the error log, the rest are aggregated into a single error message:

During the last time interval 257 query notification errors were suppressed.

Which is preceded by the message:

Error: 9245, Severity: 16, State: 1.

Prior to SQL 2012 I do not believe the error notifications were aggregated at all, and did not result in a severity 16 error.

Sql-server – Receiving error Error: 18059, Severity: 20, State: 1 in the SQL Logs

The post that Roni Vered referred to in 2013 did not say simply say: "change the connection pooling in the application's connection string."

The text said to that there was a problem with using "an Application Role ... with connection pooling." The answer was: Turn Off Connection Pooling.

This could be done in the application's connection string by including "; Pooling=False".

This worked back in the mid-2000's. Likely it will still work for you if you are still using SQL Server 2008.

The no longer correct path to the original post was: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=473777&SiteID=1

A suggested workaround from 2007: On each call if the approle is already in use, then skip the setting of the approle again. Sample code:

IF NOT EXISTS (SELECT * FROM sysusers
    WHERE name = USER_NAME()
     AND isapprole = 1)
 EXEC sp_setapprole ...

Best Answer

Related Solutions

Sql-server – Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed

Sql-server – Receiving error Error: 18059, Severity: 20, State: 1 in the SQL Logs

Related Question