DBCC CHECKDB

1) What are the risks in not running DBCC CHECKDB over your SQL server?

2) What exactly is it checking for? What will the ouput tell you?

3) How often should/do you run it?
LVL 3
pma111Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pcelbaCommented:
DBCC CHECKDB is good to use periodically (let say every month) and each time the database needs some maintenance, e.g. slows down etc.

This article answers almost all your questions: http://www.sql-server-pro.com/dbcc-checkdb.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Naranthiran DSystem AdministratorCommented:
1)Database might get corrupted at any time due to hardware problem or some issue.

2) It checks the logical and physical integrity of all the objects in the specified database.And output will provide you status of the database.

3)How frequently you should perform these runs depends on individual businesses and their production environments.
0
pma111Author Commented:
What exactly causes the corruption and how common is it.

What is the overall risk of corruption to your data?
0
alanccwCommented:
It will check the integration of the MDF database. For example, whether the checksum in the page is correct. You can refer to http://technet.microsoft.com/en-us/library/ms176064.aspx for detailed info
0
pcelbaCommented:
What exactly causes the corruption and how common is it.
The data corruption may cause bug in your (or Microsoft's) code, a virus, an attacker, or hardware failure or power failure. You may suppress each of these factors by appropriate security settings and maintenance procedures and also by your hardware conditions. To install SQL database on a standalone computer with one single disk w/o UPS means high risk.

The overall risk depends on the backup frequency primarily. DBCC can signal starting hardware problems. Even broken network card can swap certain bit values which is hard to diagnose and hard to fix in data...

etc. etc.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.