We are suddenly getting a lot of errors in a 160GB database along the lines of SQL Server detected a logical consistency-based I/O error
This seems to have started happening around 02:00 on 14/08/17 when a 'Rebuild Index' job failed
Date 14/08/2017 02:00:00
Log Job History (Epro Index Rebuilding)
Step ID 1
Job Name Epro Index Rebuilding
Step Name Rebuild Indexes
Sql Severity 24
Sql Message ID 3621
Operator Net sent
Retries Attempted 0
Executed as user: NT AUTHORITY\SYSTEM. SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:20529816; actual 0:0). It occurred during a read of page (1:20529816) in database ID 7 at offset 0x00002728530000 in file 'F:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\EproPat.mdf'. Additional messages in the SQL Server error log or system event 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. [SQLSTATE HY000] (Error 824) Executing ALTER INDEX ux_patients_history_versions ON dbo.t_patients_history REBUILD - fragmentation currently 30.2339% [SQLSTATE 01000] (Error 0) Executing ALTER INDEX in_clinic_appointments_patient ON dbo.t_clinic_appointments REBUILD - fragmentation currently 29.7339% [SQLSTATE 01000] (Error 0) Executing ALTER INDEX ux_patients_history_previousVersions ON dbo.t_patients_history REBUILD - fragmentation currently 29.0101% [SQLSTATE 01000] (Error 0) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
I've imported the latest backup onto a test SQL instance and run dbcc_checkdb and attached the results of that.
Not sure what has caused this, or if I can repair it easily!