Jorriss.com

Database Design Disasters

Not every system has a database architect available to design it. But what happens when developers design database and don’t take the proper care into designing a database? This session will take a real-world look into my experiences with some database design choices. In this interactive session, we’ll take a deep look into these design choices including a detailed discussion on why they didn’t work and what could have been done better. We may even take a peek into SQL Server internals. If you’ve ever needed to read or write to a database you’ll learn some valuable lessons from this session.

Demo code is available on Github.

Richie Rump

// about the author

Richie Rump is a Dataveloper.

Richie Rump is a principal software engineer and software architect with more than two decades spent at the intersection of application code and the data layer. He builds and operates data-intensive products, including database diagnostic tools, cloud-native serverless platforms, and full-stack applications, owning them from architecture and database design all the way through to production. Beyond the day job, he created StatisticsParser.com, co-founded a user group, and co-hosted the Away From The Keyboard podcast. On this site, he writes about performance, database internals, and the engineering practices behind reliable systems.