DBCC Optimization Tips
 |
(Alexander Chigrik) Here are some helpful tips to ensure you optimize the DBCC commands in the most efficient manner possible. |
|
| | Related Articles - For Members.
|
|
Key (Please note):
(R) - registration may be required for access at the target site
($) - target site may require paid membership for access to this or other content
Reader Comments: Post Your Comments/Feedback
RE: DBCC Optimization Tips
(posted: 3/24/2004 7:18:17 PM)
Using DBCC CHECKDB isn't always better than individual DBCC CHECKTABLE statements. If you have a large database (lots of tables and/or large tables), it can take a while to process the command, and you may not want such a performance hit on your server. I'm currently portioning tables out, and running the check on groups of tables at different times, to spread out the load. I'm also running running the checks at different frequencies, depending on the data usage frequency.
RE: DBCC Optimization Tips
(posted: 3/24/2004 7:18:44 PM)
Something else that I've discovered concerning CHECKTABLE and CHECKDB - they can only do repairs if the database is in single user mode, which makes it difficult to automate, and the integrity checks in the Database Maintenance Plans pretty useless, as far as I can tell, unless you have it send you a report every time that you actually look at.
RE: DBCC Optimization Tips
(posted: 3/24/2004 7:18:57 PM)
I'm working on an automated process that will run checks on tables according to a specific schedule, and email a report to the DBAs. That way, when there's a problem, we'll know about it (if we look at the reports), and be able to fix it manually. Hopefully we'll be able to solve problems with some scheduled downtime before we have unscheduled downtime.
|
