Brent Ozar

Production is slow. Development is fast. The same query runs in both. Somewhere between the two, a performance demon is hiding—and this session is about hunting it down.

AI is showing up everywhere in the data world—but whether it feels like a helpful sidekick, a powerful hero, or a looming villain depends a lot on your role, your skills, and the choices you make.

Ever wonder how somebody else does it? In this all-demo session, watch over Brent Ozar's shoulder while he takes a slow stored procedure in the Stack Overflow database, analyzes it, and iterates over several improvements trying to make it go faster.

Production is slow. Development is fast. The same query runs in both. Somewhere between the two, a performance demon is hiding—and this session is about hunting it down.

Ever wonder how somebody else does it? In this all-demo session, watch over Brent Ozar's shoulder while he takes a slow stored procedure in the Stack Overflow database, analyzes it, and iterates over several improvements trying to make it go faster.

You're constantly loading new sales data in, but when users run reports for recent sales like today or yesterday, you get bad query plans. Brent Ozar will explain how statistics are involved, why you can't update them frequently enough to get it right, and how trace flags 2389 and 4139 help performance.

When you’re facing lock waits and blocked queries, it’s tempting to just slather NOLOCK all over the queries. Thing is, this won’t necessarily fix it, and there are much better ways to track, diagnose, and cure blocking issues.

Ever wonder how somebody else does it? In this all-demo session, watch over Brent Ozar's shoulder while he takes a slow stored procedure in the Stack Overflow database, analyzes it, and iterates over several improvements trying to make it go faster.

You’ve downloaded sp_Blitz, sp_BlitzIndex, and sp_BlitzCache from the First Responder Kit,and you’ve run them a few times. You know there’s a ton of advice in there, but…it’s kindaoverwhelming.

For years, you've heard that you're supposed to reorganize your indexes to make SQL Server go faster. It sounds like it makes sense - keep things in order, right?

You swear nothing has changed, but all of a sudden, out of nowhere, queries that used to be fast are suddenly slow. Even weirder, you take the slow query from the application, run it in SSMS, and it's totally fast!

You haven't installed SQL Server 2019 yet, and you don't want to sit through a bunch of slides. You want to see a series of real-world demos focusing on the features of SQL Server 2019 that will make your users happier with as little work as possible on your part.

“Is something going on with the SQL Server right now?” You hear those words, and your heart starts to race a little faster. You try to connect to the SQL Server, and it responds, but you can tell it’s a little slow.

You haven't installed SQL Server 2019 yet, and you don't want to sit through a bunch of slides. You want to see a series of real-world demos focusing on the features of SQL Server 2019 that will make your users happier with as little work as possible on your part.

You're comfortable writing T-SQL, and you've built a lot of stored procedures that have a bunch of parameters. For example, you have that "product search" stored proc with parameters for product category, name, price range, sort order, etc, and you have to accept any of 'em.

You haven't installed SQL Server 2019 yet, and you don't want to sit through a bunch of slides. You want to see a series of real-world demos focusing on the features of SQL Server 2019 that will make your users happier with as little work as possible on your part.