1

Topic: Interesting error

As if the DB broke. Application refuses to work with basis. In a broad gull of an error of type:
Error: 824, gravity: 24, a state: 2
SQL Server detected a logical consistency-based I/O error: a protection invalid parameter. It occurred during a to read of page (1:529) in database ID 7 at offset 0x00000000422000 in file
Thus checkdb produces:
Msg 8921, Level 16, State 1, Line 1
Check is cancelled. In the course of collection of the facts the error has been found out. Probably, the tempdb database reached a storage limit, or the system table is not coordinated. Check up the previous errors.
But at same probably to make  and recovery of a DB, the table open, the data is read. Other DB on the same server works normally,  transits regularly. What can it be?
SQL2008r2sp2 express, win2003

2

Re: Interesting error

https://support.microsoft.com/ru-ru/hel … puter-that

3

Re: Interesting error

Well, it is possible to bypass. For localization of a problem business good...
But search found already problem table. But all is deafly similar:
Msg 824, Level 24, State 2, Line 1
The SQL Server found out the logical error of input-output connected to a coordination: a protection invalid parameter. It happened at to read pages (1:528) in a database with the identifier 7 on offset 0x00000000420000 a file "C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\DB51_2.mdf". Additional convergence see in the error log of a SQL Server and log of system events. It is a hard error which threatens integrity of a database and should be immediately corrected. Fulfill the full check of a database on a coordination (DBCC CHECKDB). This error can be caused many reasons; additional convergence see in the electronic documentation on a SQL Server.
It  at treatment attempt already

4

Re: Interesting error

Then checkdb + repair_allow_data_loss
And-or to create new basis/table and to pour the data there.