0

SharePoint switches OFF and ON options like AUTO_UPDATE_STATISTICS, AUTO_UPDATE_STATISTICS_ASYNC, AUTO_CREATE_STATISTICS, INCREMENTAL on SharePoint databases daily at 12 AM and that generates lots of noise in SQL Server error log.

What action should I take(Either in SQL Server or in SharePoint) to keep the error log clean?

3
  • Ignore or filter-out the messages you don't care about?
    – Hannah Vernon
    Commented May 28, 2019 at 11:53
  • There are no settings in SQL Server to stop specific log messages from being written to the error log. You might want to check to see if there is a setting in SharePoint to stop it from making these changes. Commented May 28, 2019 at 14:57
  • I check the error log of all the instances once everyday and some times I overlook critical events in the log because of so much noise as there is no visual indication between informational, warning and critical. In filter there is no option to exclude and once you close the windows all filter settings are lost.
    – shilan
    Commented May 29, 2019 at 6:52

2 Answers 2

1

In case someone else will google it. I disabled the Health Analyzer Rule Definitions with name "Databases used by SharePoint have fragmented indices."

Also I disabled the following timerjob

Name                        : daily-all-spwebservice-health-analysis-job
TypeName                    : Microsoft.SharePoint.Administration.Health.SPHealthAnalyzerJobDefinition

After that events gone.

1
  • Better to live with the ”noise” than turn off essential maintenance furthermore you probably make your sharepoint unsupported if you stop it running the supplied jobs. Commented May 15 at 12:39
0

from the comments

I check the error log of all the instances once everyday and some times I overlook critical events in the log because of so much noise as there is no visual indication between informational, warning and critical.

I'm with you on that! SQL Server's error log is often full of nonsense, and the search GUI is an absolute relic. If Microsoft isn't careful, it'll end up in a British museum.

That's exactly why I wrote sp_LogHunter. It's designed to wander through error logs looking for important messages, and excluding most of the noise. You can read the full documentation for it here, but a simple example run would just be:

EXEC sp_LogHunter;

That will go back (as a parameter default) seven (7) days looking for interesting messages.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.