2025-10-29
2025-10-29
In this Article , We will delve into the world of Query Store and explore how to use Optimized Plan Forcing to improve performance in SQL Server 2022. We will discuss what it is, how it works, and how it can impact your system's performance.
2023-09-04
5,201 reads
2022-10-26
433 reads
he SQL Server Database Engine processes queries on various data storage architectures such as local tables, partitioned tables, and tables distributed across multiple servers. The following sections cover how SQL Server processes queries and optimizes query reuse through execution plan caching.
2022-09-23
In this tip we look at how to save an execution plan for future review as well as using the full screen mode to see more of a query plan at one time.
2020-08-18
Starting to translate sp_BlitzCache into the cloud.
2018-07-27
4,046 reads
Brent demos a single query plan that asks for 2 identical indexes on the same table.
2017-12-26
3,142 reads
Rob Farley looks at information exposed in query plans about residual predicates and actual rows read, showing how Plan Explorer helps identify the issue.
2016-07-20
3,121 reads
SQL Server keeps the most-used execution plans in cache, so it doesn't need to recompile the same queries every time. How can we benefit from this to find potential performance problems in execution plans?
2015-01-13
9,693 reads
2011-10-27
2,279 reads
By Steve Jones
I’ve often done some analysis of my year in different ways. Last year I...
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
I have a couple of SQL Agent job steps which run PowerShell commands of...
Comments posted to this topic are about the item Database security permissions save script
I have a SQL Agent job for backing up a set of Analysis Services...
I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?
See possible answers