In theory, SQL Server performance monitoring is pretty simple: 1. Review the server’s top wait types, 2. Find the queries causing those wait types, 3. Fix those queries, or improve the way the server reacts to them (indexes, settings, etc.). But in practice, step 2 is awful because:
2026-05-13
Learn about a new feature of SQL Server 2022 - Parameter Sensitive Plan Optimization(PSPO)
2025-09-15
2,129 reads
Learn about the SQL Server plan cache and how SQL Server caches query plans, and the potential of plan cache bloat which could impact performance.
2024-04-10
How often do you check your query plans to see if they contain any warnings? If you're missing them, it means that you're not getting all those hints about missing indexes, join predicates or statistics. Is the query optimiser trying to tell you about implicit conversions? Dennes shows how to view the warnings in plan cache for a particular database using SQL.
2015-03-02
7,649 reads
This script will return all the Adhoc Single use Plans currently in your Plan Cache.
It also excludes Plan Shells created from auto/forced parameterization. Works for 2005/2008
2012-12-11 (first published: 2012-11-26)
853 reads
By Steve Jones
I had seen these roles in various instances, but never dug into the new...
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Comments posted to this topic are about the item Pay for Performance, which is...
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers
