Forum Discussion
Corrupt table in database
get this error after select script "SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x1004cd6e). It occurred during a read of ...
Hi Tiyanjana,
The causes of this issue could be
1- file system corruption
2- hardware system issues including storage, SAN, disk, raid controller, etc.
3- driver issues
4- corrupted memory pages
5- problems with the SQL Server Engine.
For fixing it, you can use the steps in this Microsoft article:
https://docs.microsoft.com/en-US/troubleshoot/sql/admin/troubleshoot-dbcc-checkdb-errors
The causes of this issue could be
1- file system corruption
2- hardware system issues including storage, SAN, disk, raid controller, etc.
3- driver issues
4- corrupted memory pages
5- problems with the SQL Server Engine.
For fixing it, you can use the steps in this Microsoft article:
https://docs.microsoft.com/en-US/troubleshoot/sql/admin/troubleshoot-dbcc-checkdb-errors
The main cause behind the corruption is logical consistency for this error for the SQL server.
This error comes when the Database file has been corrupted.
For this, you can follow the steps for fixing the database through this:
https://community.spiceworks.com/how_to/190952-how-to-troubleshoot-database-consistency-errors-reported-by-dbcc-checkdb
I hope this would help.