November 13, 2013 at 7:20 am
jfogel (11/12/2013)
I got it right not because I actually knew the answer but because I figured that the data (meaning common) pages would be fixed by automatic page repair while more high-end issues would not. The logic being that the more you need it the more likely it wont happen.
+1 (same here)
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
December 19, 2013 at 2:44 am
seems to be logical answers +1
March 6, 2014 at 4:53 pm
Thanks, easy question as I have seen the automatic page repair live in a production system. It's a really cool feature. The status of the corrupt pages are stored in a table that you can Query to see if they are fixed or not.
First time I saw it, I was really surprised as I got an error in a Query that tried to select a corrupt page, but when I ran DBCC CHECKDB the corruption was gone.
/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
MCSE: Data Platform
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply