For this month's T-SQL Tuesday, I talk about a not-quite-yet-announced feature in SQL Server 2022 that has the potential to function as a low-effort bad habit logger.

While I previously promoted a way to stop storing database name in your Extended Events sessions, there's an upside to collecting it: the ability to filter. Read on for more info.

I talk about a trade-off when using collect_database_name for DDL events captured by Extended Events.

See two ways you can make the relevant data in the system_health session last longer and not get drowned out by noise.

Access the system_health file target without tedious string parsing gymnastics.

I finish up my series on replacing the default trace with views to simplify consumption and a caveat about reports in SSMS.

I continue my series on replacing the default trace with a more efficient and more complete Extended Events session.

I start a series explaining how I evaluated the default trace and decided to replace it with a slimmer Extended Events session across all of production.

See how you can use Extended Events to find your worst performing checkpoints.

A quick post to show how to pull autogrow events from the default trace.