Chances are good, no, great that your application’s database layer contains a few design problems, like:
- Index Shotgun
- Keyless Entry
- Fear of the Unkown
- Spaghetti Query
Not sure? Don’t worry, this book will help you and your team find poor design patterns and show you how to fix them. I’ve worked on numerous projects that were started on by one developer, worked on by an assortment of other devs and then finally taken over by me. Everyone has their own approach to Database structure and design, but rest assured, there are right and wrong ways to architect a SQL database.
Some design flaws are simple, like trying to build quality database relationships without a pivot/linking table… the current system I work on has plenty of that. Too often a SQL database is created like a bunch of shoe boxes, used to throw tons of data into but no forward thought as to how that data needs to come out or maintained. SQL Antipatterns by Bill Karwin
This is a great coder source: SQL Antipatterns: Avoiding the Pitfalls of Database Programming
Each chapter of the book will help you identify issues, explain antipattern scenarios, and correct unique and even dangerous design antipatterns.
