Part of good server monitoring it to have alerts enabled for a number of different errors to know when things go bad. The problem is we were getting the following error every time the server was restarted.
SQL Server Alert System: ‘ERROR 824’ occurred on \\MyServerName
DESCRIPTION: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xe660dd36; actual: 0xcd481907). It occurred during a read of page (1:8939) in database ID 7 at offset 0x000000bcef6000 in file ‘C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\mydatabase.mdf’. Additional messages in the SQL Server error log or operating system error log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Since we have had SQL alerts enabled for ERROR 824, this alert had been sent every time the SQL instance was restarted, around 8 of them, but it had been more than a year since we had repaired the corruption had been repaired. After some investigation I found that the Windows Event log had not been cleared in a few years.
Clearing the event log has cleared out these old messages so that we no longer get notified of old corruption on every restart.
Keep in mind that after repairing a corruption issue if you have alerts enabled, you may want to clear out your event log (application) so that you don’t get any of these old messages.
Need help with Database Corruption Repair, Stedman Solutions can help. That’s what we do.
More from Stedman Solutions:
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!