can database design or DML be cause of data corruption (other than obvious possibility of Disk issues)?

can a db design issue cause? is it possible?

one of the reason I ask is every 6-8 months, one database seems to be corrupted.. I can't say that for any of the other databases on that sql instance. (the one that gets corrupted is active (meaning being used), the others are more for archives though and occasional querying).
LVL 5
25112Asked:
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.

25112Author Commented:
article in sqlmag says
"In virtually all cases of SQL Server database corruption (over 99.99% by most accounts), the root cause of corruption is due to problems at the IO subsystem level"

what are the other 0.01% causes?

a)can a poorly designed database ever possible to cause data corruption? (that checkdb reports)?

b)can stored procs, functions (DML) Deletes Inserts cause (is it possible) data corruption?

c)is the answer to the above the same for physical disk as well as virtual?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
What you mean with 'data corruption'? Is data lost? Or can't access to data?
DBCC CHECKDB should be run regularly over all databases to check the data integrity.
A good backup policy should be set in case of the need for a recover to avoid big data losses.
0
25112Author Commented:
'data corruption'- yes, referring to 'data integrity' errors that CHECKDB gives.

question is other than the 99% rootcause of disk issues, can DML ever cause the data integrity, in the first place.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I don't think DBCC CHECKDB command will track bad data models. What it usually do is to check if all referential integrities rules are 100% OK (broken FK's or other Constraints) and physical corruptions (access to data and BLOB files).

If you have a database without PK, FK and any kind of indexes, DBCC CHECKDB won't throw an error because of that.
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
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
Storage Hardware

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.