February 5, 2009 at 11:53 am
might be a more insight
note down the offset value and open scientific calc
select hex and type the offset and change to decimal and divide by 8192 and get the page number.
Run dbcc page and get the object_id and feed that object id in the sysobjects table and find which is that object...
might help..
but fix IO subsystem...
as we say ..once bitten twice shy...make sure you tune up your IO
February 5, 2009 at 7:03 pm
Waste of time - I already time him where the corruption is - in one of the critical system tables, that he can't do anything about. I wrote that error message so I know which tables it was trying to read.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply