"Failed integrity check" in Change Log

by Sep 10, 2015


I have a nightly process that runs this command for each of our audited servers: SQLCMCMD checkintegrity <AuditedServerName>.

One of our five audited servers had a “Failed integrity check” in the Change Log one night over the Labor Day weekend. It worked successfully the next night with nothing being done on our part. It has not happened again since then.

It just happens that our auditors are in town, they noticed it, they would like to understand this and what we do about it. Honestly, I have never done anything when I have had one fail. Can someone please explain how this should be handled?