On a .NET web app, we are using ChangeMonitor to update caches on data change at SQL Server 2012 database. And change monitor relies onSqlDependency.
When you call the SqlDependency.Stop method, the method does not actually cancel the notification subscription. When SQL Server sends a new query notification to the application, SQL Server cannot find the remote service. Therefore, error messages
are logged. And we have a concern that this add more noise to the SQL log and trying to avoid.
There is a kb article for this for SQL Server 2005 and 2008. Actually its not a fix but workaround for not logging the error in SQL Log with use of trace flag 4133. https://support.microsoft.com/en-sg/kb/958006
1. Is there a fix for this for SQL Server 2012?
2. Is it recommended to use this trace flag(4133) for SQL Server 2012, wouldn't it prevent the genuine error messages?
Thanks for your support