|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 7:57 AM
Points: 47,
Visits: 183
|
|
Grant Fritchey (8/23/2011) Excellent code. Nice article. Well explained.
But I have to say, articles like this really do make me nervous. It seems like a very healthy percentage of our fellow database professionals are missing a few fundamentals. Suggesting a way to avoid something as important as DBCC CHECKDB seems rife with potential for disaster. I'd just hate to hear "I was following your advice and now we've lost our production system."
This.
Also, the only way for DBCC CHECKDB to be faster is for Microsoft to fix tempdb so that DBAs can allocate filegroups to temporary storage on a per database (or perhaps even more granular) basis. A global tempdb database used for everything is simply the biggest design flaw in SQL Server today, period.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 4:31 AM
Points: 1,
Visits: 117
|
|
Come on guys, this is not recommended as an alternative or replacement. It has to be better than doing nothing inbetween the usual 7 days to a month gap DBCC runs on large DB's
Credit to you Ian!!
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, June 11, 2013 2:31 AM
Points: 9,
Visits: 48
|
|
yemi_aderele (9/9/2011) Come on guys, this is not recommended as an alternative or replacement. It has to be better than doing nothing inbetween the usual 7 days to a month gap DBCC runs on large DB's
Credit to you Ian!!
I agree with Yemi, although I will also not use it because of the DBCC DROPCLEANBUFFERS. Especially liked the idea of the whole check stopping early when an error is detected.
|
|
|
|