The process of query optimization is very computationally expensive. For this reason, SQL Server stores execution plans in a cache (called the plan cache), so that the stored execution plan is ...

As I discussed in an earlier column, SQL Server keeps a plan cached for each query it sees (assuming the query requires planning in the first place, of course). That's great for speeding up processing ...

The first step is to look at the execution plan for the query and see if there are any glaring problems. Put the query in a new query window in SQL Server Management Studio. Looking at the ...

Prior to SQL Server 2017, query processing was a monolithic process. The SQL Server query optimizer would first construct a query plan for a batch of T-SQL code, a stored procedure, or function and ...

This is a good thing because, in our applications, the same queries do keep coming around again and again. So, once a plan is created, SQL Server flags it with a couple of identifiers that tie the ...

The SQL Server query optimizer estimates the cost of running a query plan using the number of rows that will be processed, which is the cardinality for the query. There are some queries where it ...

This facilitates SQL Server Query Store's enablement of query hints ... Another feature, called Parameter Sensitive Plan Optimization, automatically enables the generation of multiple active ...

The following query can be used to determine the recovery model of the databases on your SQL Server instance ... as part of your database maintenance plan. If your database recovery model is ...

SQL Server 2005 has under a year until it reaches end-of-life status, where there will be no further updates for security purposes and no official support available from Microsoft. Meanwhile, IT is ...

SOS_SCHEDULER_YIELD—SQL Server instances with high CPU usage often show the SOS_SCHEDULER_YIELD wait type. This doesn’t mean the server is underpowered; it means further research is needed to find ...