August 6, 2015 at 12:18 am
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xd6715d3a; actual: 0xd6715d2a). It occurred during a read of page (1:498) in database ID 14 at offset 0x000000003e4000 in file 'G:\GAStaffing.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. (.Net SqlClient Data Provider)
Showing This Error
August 6, 2015 at 12:29 am
Restore from your last good backup (backup before the corruption happened)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 6, 2015 at 12:40 am
only one back up i have..
If der any posibilty.
August 6, 2015 at 12:50 am
Then you have a serious problem.
Run the following, post the full and complete, unedited output.
DBCC CheckDB('<Database name>') WITH NO_INFOMSGS, ALL_ERRORMSGS
Do not do anything else to the database.
You may want to go and tell management, or the owners of the database, that due to the lack of backups there may be significant downtime, data loss or both.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 6, 2015 at 1:01 am
Thanku !! yes i wil Inform
August 6, 2015 at 1:07 am
wt is d use of thar query
August 6, 2015 at 4:11 am
It does a consistency check of the database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 6, 2015 at 4:20 am
showing some Err
August 6, 2015 at 4:24 am
GilaMonster (8/6/2015)
Run the following, post the full and complete, unedited output.
DBCC CheckDB('<Database name>') WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 5, 2015 at 12:41 am
This was removed by the editor as SPAM
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply