Top 10 transactional database mistakes, and how to avoid them
summary
A concise checklist of ten real failures and fixes: missing relational design and duplication (move tables to third normal form), absent surrogate keys (add identity primary keys), destructive deletes (use soft deletes or change tracking), no created/updated timestamps, lax data types and checks (add constraints), cascades of triggers and bad hierarchies (consider hierarchyid), too many or too few indexes, row-by-row cursors (replace with set operations), and dynamic SQL risks — replace volatile queries with CRUD stored procedures to cache plans and stop SQL injection.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:54What are transactional databases
- 3:13Normalisation
- 5:19Identity
- 6:37Hard delete
- 8:27Columns
- 9:00constraints
- 9:58triggers
- 10:53hierarchy IDs
- 12:12indexes
- 12:50curses
- 13:41Dynamic SQL
- 15:38Summary
related talks
31m10 Costly Database Performance Mistakes (and How to Fix Them)
35m10 things a developer should know about databases
39m10 Things Developers should know about Databases
51mWorking with Database Transactions the Right Way
05mAfter analyzing 600,000 SQL queries, these are the top mistakes developers make
51mThe Lost Art of Database Design
45mBest Practices for Optimizing Database Projects
05mCommon mistakes of DBAs