SQLBits 2023

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.

Data growth can easily become a problem soon after deploying a database in production, especially if data layout and data management was not planned. 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. Will combining partitioning, temporals, CSI, and other indexing with different loading/unloading/deletion make it possible? The session starts by defining the frame requirements coming from real projects and goes through different alternatives and possible solutions, their benefits, and drawbacks. 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.

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!

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.

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.