PSP optimization

SQLServerCentral Article

Exploring Parameter Sensitive Plan Optimization in SQL Server 2022

  • Article

PSPO (Parameter Sensitive Plan Optimization) is a SQL Server feature that improves query performance by accepting varied data sizes based on the runtime parameter value(s) specified by the customer. It deals with the situation in which a single cached plan for a parameterized query isn't the best option for all potential incoming parameter values. Non-uniform data distributions exhibit this phenomenon. When using PSPO, SQL Server keeps several execution plans for a single query, each one customized for a particular parameter value. With the help of this feature, numerous execution plans for a parameterized query are generated, each of which is tailored for a certain range of parameter values.

You rated this post out of 5. Change rating

2023-07-21

4,725 reads

Blogs

Learn about Modern Microsoft Apps in San Diego

By

I wrote about learning today for the editorial: I Can’t Make You Learn. I...

How To Deploy Fabric SQL and Azure SQL Databases with Azure DevOps

By

Fabric has CI/CD built in, but if you've tried to use it for database...

A New Word: Attriage

By

attriage – n. the state of having lost all control over how you feel...

Read the latest Blogs

Forums

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

TRY_PARSE vs TRY_CONVERT in SQL Server: From Basics to Practical Usage

By john.martin

Comments posted to this topic are about the item TRY_PARSE vs TRY_CONVERT in SQL...

DBCC CHECKDB Limits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits II

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers