Margarita Naumova

Magi Naumova is an SQL Server Architect and Consultant, speaker and trainer, Microsoft Certified Master, MVP, MCT, Founder of SQL Master Academy, and founder and CEO Of Inspirit Data Platform Consulting Company in Bulgaria and Norway, founder, and the leader of Bulgarian SQL & BI User group and Azure Analytics User Group BG. She has more than 25 years SQL Server training and consulting experience. Magi is a former member of Microsoft Services Worldwide Technical Leadership Team. Currently she speaks, writes, trains and consults people on SQL Server and MS Fabric Data Platform. She is MVP for 15 years in a row. Her unique SQL Master Academy training program has helped hundreds of specialists to feel knowledgeable in their daily work or to find an inspirational career path in the world of SQL Server.

Sessions for 2026

From Load to Logic: Designing for Performance in Microsoft Fabric Warehouses

This training day provides an end-to-end approach to designing high-performing Microsoft Fabric Warehouses. It covers loading strategies, schema and query design, performance features, Workload Management, and deployment practices, with a strong focus on performance and cost efficiency. Real project examples and feedback from data engineering teams illustrate how design decisions behave in practice. Attendees leave with a clear mental model that enables informed, scalable, and predictable warehouse design.

A Deep Dive into Table Partitioning – Part 1: Mechanics and Performance

A practical, demo-driven deep dive into SQL Server table partitioning. Learn how partitioning works under the hood, why partition elimination succeeds or fails, and how design and maintenance choices impact performance and reliability in real systems. Learn how table partitioning works internally in SQL Server. This Part 1 session covers partition functions and schemes, physical row placement, partition switching, splitting and merging, and the mechanics behind partition elimination—supported by practical demos and execution plan analysis.

A Deep Dive into Table Partitioning – Part 2: Design, Maintenance, and Troubleshooting

A practical, demo-driven deep dive into SQL Server table partitioning. Learn how partitioning works under the hood, why partition elimination succeeds or fails, and how design and maintenance choices impact performance and reliability in real systems. Learn how table partitioning works internally in SQL Server. Build on the partitioning mechanics from Part 1 and focus on real-world usage. This session explores partition key selection, aligned and non-aligned indexes, maintenance strategies, and how to diagnose and fix common performance problems in partitioned tables.

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

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.