Solved

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

Posted on 2014-09-18
4
166 Views
Last Modified: 2014-10-07
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).
0
Comment
Question by:25112
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 5

Author Comment

by:25112
ID: 40330295
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
 
LVL 50

Expert Comment

by:Vitor Montalvão
ID: 40330428
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
 
LVL 5

Author Comment

by:25112
ID: 40330724
'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
 
LVL 50

Accepted Solution

by:
Vitor Montalvão earned 500 total points
ID: 40332043
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

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Storage devices are generally used to save the data or sometime transfer the data from one computer system to another system. However, sometimes user accidentally erased their important data from the Storage devices. Users have to know how data reco…
Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question