Database Architecture Antipatterns and Fails

Kevin Kline

Designing a high-performance database application isn’t easy. There are so many distinct areas of the architecture that can under perform or, worse, degrade performance in other areas of the application. In this session, we will cover the most common antipatterns and architectural failures on relational database applications, from the logical design of the data model, to indexing, to SQL code, to infrastructure, to resilience, and beyond.

This session clears up the most common misunderstandings about how SQL Server and other relational databases work, so that your future designs can ensure better performance, longer up-time, and faster recovery. In each of our example “awful architectures”, we will cover:

– What was the original goal or requirement the example tried to solve?
– What was the resulting architect?
– How to recognize the antipattern in existing applications?
– What’s the best solution to meet the original requirements?

This fast-paced session takes you through a variety of “awful architectures” seen over many decades of experience of the speakers. Some will make you laugh, roll your eyes, or even groan out loud! You’ll not only learn what to avoid but, in the process, learn what works best for database applications running on SQL Server.