Intermittent performance issues due to parameter-sensitive queries are a DBA’s nemesis. By the time you’re notified of an issue, sometimes it’s gone away…or someone else has restarted the instance or cleared the plan cache, and any data you could use is gone. Capturing the different plans for those queries can be tricky, but with Query Store it becomes very simple – the hard part is deciding what plan you like best. The Query Store feature, introduced in SQL Server 2016 and also available in Azure SQL Database, captures query performance data, and it allows you to manually force a plan for a query. In SQL Server 2017 and Azure SQL DB, the Automatic Plan Correction feature will force plans for you. Sound scary? It’s not. In this session we’ll explore both manual and automatic plan forcing through demos so you understand how it works, what to expect, and what to watch out for when you implement it in your environment.
Erin Stellato, Principal Consultant SQLskills
Erin Stellato is a Data Platform MVP and lives outside Cleveland, OH. She has almost 20 years of technology experience and has worked with SQL Server since 2003. Her areas of interest include performance tuning, Query Store, Extended Events, and helping accidental/involuntary DBAs understand how SQL Server works. Erin is an active member of the SQL Server community, has volunteered for PASS at the local and national level, and is a regular speaker at conferences including the PASS Summit, SQLIntersection, and SQLBits. Outside of time with family and friends, she enjoys running, spinning, movies, and all things chocolate.