Denis Reznik

SQL Server 2025 is now generally available, packed with headline-grabbing features like built-in AI capabilities, Microsoft Fabric integration, native JSON data type with advanced functions, vector database, regular expressions, and more. These features are exciting and well-covered in official releases, blogs, and…

Presented remote by Denis Reznik. Yes, you’ve heard this correctly. This is precisely a detective story, even a few stories. Each of them has an intricate plot, several active (or inactive) persons, facts, clues, and evidence. During the session, we will solve all these cases and complete a path from obtaining information (accurate or inaccurate) to a complete understanding and solution of the problem, which will allow you to feel confident in a similar situation and work more efficiently with SQL Server. I cannot disclose many details so far (you understand), but I can tell that the topics of performance tuning, blocking, and server management will take part in this detective, and the stories themselves are true.

Generally, there are only two options for query slowness: either the query itself is slow (high CPU time) or the query is waiting for some resource (high Wait time). All other reasons for query slowness are derived from these two options. In this session, we will learn how to determine what is the reason for the long-running query, what the request can wait for, and how it can be accelerated