SQLBits 2022

Modern database design (anti)patterns

We must realize that patterns which were valid 10 years ago are less likely to work now, like cursor logic, xml usage, or storing all in db v/s using NoSQL. From global industry trends to specific database patterns, this session is a combination of best practices, good and bad patterns, tips, and tricks which I give to customers in my work as a consultant.

The database tier is quite often neglected in the application design process, which results in performance issues, lack of scalability and even disruption of service. Design choices that seem great at the beginning fail totally on scale and performance when the application goes in production. We must realize that patterns which were valid 10 years ago are less likely to work now, like cursor logic, xml usage, or storing all in db v/s using NoSQL. From global industry trends to specific database patterns, this session is a combination of best practices, good and bad patterns, tips, and tricks which I give to customers in my work as a consultant. Good design choices from the beginning help avoiding complex and expensive redesign in the future!

feedback link: https://sqlb.it/?7315

Margarita Naumova's other proposed sessions for 2026

Large Tables, Big Problems: Indexing, Partitioning, and Archiving at Scale - 2026

Margarita Naumova's previous sessions

Keeping historical data in tables forever – mission (im)possible!

Let’s discover some solutions for keeping historical data in the database when you receive near to impossible requirements like storing data in same tables forever and being able to edit and query them at the same time, of course keeping the response at its best. Based on a real project case the session walks you through the design process from the start to the reaching of the final solution and making the client (and developers) happy.

Modern database design (anti)patterns

SQL Server Table partitioning – DOs and DON’Ts

When do we get improvement in the performance, and when should we better not choosing partitioning but some other optimization techniques instead? Shall we optimize by using partitioning or yet another index?

Identify opportunities for In-Memory OLTP

The session will uncover the In-Memory OLTP architecture, the concerns about data durability and database startup and recovery as well as some important consideration on Management of in-memory objects.