Data corruption
Data corruption is the unintended alteration, loss, or damage of data that makes it inaccurate, invalid, inconsistent, or unusable.
100 SQL Server Mistakes and How to Avoid Them
Database corruption is an invalid or inconsistent state in which stored database structures or data no longer conform to their required format or integrity constraints.
- How it is used
- Uses regular corruption checks to prevent database failures from becoming business-impacting incidents.
- How deep it goes
- Explains causes, consequences, detection, and safe failure simulation, but stops short of detailed repair procedures.
- Examples
- Uses the MagicChoc incident, MarketingArchive, DBCC CHECKDB, and a deliberately corrupted ImpressionsArchive data page.
- What you can do after
- Diagnose corruption with DBCC CHECKDB and recognize safeguards required for controlled SQL Server failure testing.
Read how 100 SQL Server Mistakes and How to Avoid Them explains data corruption →
Software Security for Developers
Data corruption is unintended alteration or loss of stored or transmitted data that makes it differ from its correct contents.
- How it is used
- Uses hash comparison to prevent corrupted refund files from driving payment processing.
- How deep it goes
- Explains hash generation, comparison, rejection, and accidental-failure limits, but defers active-tampering protection.
- Examples
- Uses refunds.json, sidecar hash files, Maven Central artifacts, Git commits, and a Java refunds endpoint.
- What you can do after
- Diagnose accidental file corruption by recomputing a hash and rejecting mismatched content.
Read how Software Security for Developers explains data corruption →
PostgreSQL Mistakes and How to Avoid Them
Data corruption is the unintended alteration of stored data so that it no longer accurately represents its intended content.
- How it is used
- Uses corruption warnings to guide PostgreSQL monitoring, recovery planning, and safe data migration.
- How deep it goes
- Traces corruption from diagnostic log symptoms through recovery controls and encoding-safe migration procedures.
- Examples
- Uses invalid-page logs, short block reads, encoding errors, iconv conversion, and cleaned migration files.
- What you can do after
- Diagnose corruption signals, preserve recoverable database states, and execute safer encoding migrations.
Read how PostgreSQL Mistakes and How to Avoid Them explains data corruption →
Related concepts
- cryptographic hashaddressed by · A cryptographic hash is a fixed-length digest computed from input data by a deterministic function designed to resist preimage, second-preimage, and collision attacks.
- data lossproduces · Data loss is the destruction, corruption, deletion, or unavailability of information that is expected to be retained or remain usable.
- stale dataproduced by · Stale data is information that no longer reflects the current state of its underlying source or relevant conditions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.