Data Integrity 2.0. The biggest advancement in data quality in 30 years!
summary
Demonstrates a working implementation of native SQL Assertions that enforce complex cross‑table rules declaratively: examples include “no employee salary above department head,” single president existence, orders must have items, and temporal no‑overlap for contracts. Assertions run at commit or defer time, support no-validate bootstrapping, reduce client‑side API complexity and often improve throughput versus app‑side checks, and use database concurrency so conflicting transactions block appropriately. Current limits: only equi‑joins, deterministic functions, three nested levels, and no aggregation or views.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:22Relational databases' limits
- 6:53Data corruption problem
- 10:43Business rules complexity
- 17:47Why databases corrupt
- 22:27Assertions promise
- 27:44Assertions in action
- 33:01Assertions performance
- 38:01Assertions and concurrency
- 40:50Assertions limitations
- 43:40Summary
related talks
35mApplying Data Quality Monitoring
41mData Quality: The Holy Grail For A Data Fluent Organization
12mNever be blocked by bad data again
55mHow Not to Destroy Data
37mData Validation at Scale: Managing Data Quality in Complex Data Pipelines
28mPerfect is too expensive
37mEngineering data quality
35mIt's Just Data