Index Tuning Decision Tree for SQL Server
Category:
query-performance
I recently mapped out my thought process for how I approach a new instance of SQL Server when it comes to index tuning.
Tag: query-store
Will Query Store Work in a Read Only Database?
Category:
query-performance
For static databases, it’s quite useful to set SQL Server’s “read only” database property to true. When the database is read-only, it ensures that the last backup you took is still valid… as long as nothing bad happens to that backup file.
Can I Force A Hinted Plan with Query Store in SQL Server 2016?
Category:
query-performance
SQL Server 2016’s Query Store feature promises to be better than Plan Guides ever were. The Query Store lets you track query performance, collect execution plans, and force a specific plan if you notice that a query is sometimes fast, and sometimes slow.
NO_PLAN and NO_INDEX: Breaking a Forced Query Store Plan
Category:
query-performance
Whenever you’ve got a new feature, one of the first things to ask is, “What happens when I break it?”
Because we’re going to break stuff.
Does Query Store Regressed Queries View Catch Nasty Parameter Sniffing?
Category:
query-performance
SQL Server 2016’s new Query Store feature has an option that looks for “regressed” query plans.
But does it catch “bad” parameter sniffing?
How to Find Missing Index Requests in Query Store
Category:
query-performance
SQL Server 2016’s new Query Store feature makes it easier than ever for DBAs and developers to identify the most important queries to tune– and perhaps apply a quick fix by pinning an execution plan.
Does OPTION (RECOMPILE) Prevent Query Store from Saving an Execution Plan?
Category:
query-performance
Recompile hints have been tough to love in SQL Server for a long time. Sometimes it’s very tempting to use these hints to tell the optimizer to generate a fresh execution plan for a query, but there can be downsides.