The problem: I was checking the query store of a database where performance testing was done.The top CPU resource consumer was a simple query on 1 table with a perfect covering index, but the query plan looked more complicated than expected. The problem? The varchar(max) datatype of parameters in the query didn’t match the data […]
Use (n)varchar(max) parameters only when you really need to. Read More »
When you use the Query Store, you could miss load on your database if query’s are launched from another database. Query’s are stored in the database from where they are launched. Let me show you this with an example. We have a query that is launched from the AdventureWorks2019 database. It doesn’t touch any resources
Cross-database query’s and Query Store Read More »
When I work with Query Store, I often need to find the executions that didn’t finish successfully, queries that were aborted or ended with an exception. In the SSMS interface, you’d normally look for a square icon (client-abort) or a triangle icon (runtime error) . Trying to find those by clicking through the dashboard is slow.
Need to quickly spot failed query’s in Query Store? Read More »
