Create a Non-Clustered Index on the CustomerID columnĬREATE NONCLUSTERED INDEX idx_CustomerID ON Sales.SalesOrderHeader2(CustomerID) SELECT * INTO Sales.SalesOrderHeader2 FROM Sales.SalesOrderHeader Create a copy from the Sales.SalesOrderHeader table In addition I have also created a Non-Clustered Index on that column.
#Adventureworks2012 query Patch#
In the next step I create a copy of the table Sales.SalesOrderHeader and patch the data so that we have a non-linear data distribution in the column CustomerID.
The last listing has already enabled Forced Parameterization for the AdventureWorks2012 database. Now let’s play with Forced Parameterization in SQL Server. Why Forced Parameterization is not always a good choice In that case, SQL Server will always auto parameterize your SQL statement except in the following cases: Let's now activate Forced Parameterization on the AdventureWorks2012 databaseĪLTER DATABASE AdventureWorks2012 SET PARAMETERIZATION FORCED If you still want to have Auto Parameterization performed by SQL Server you can enable Forced Parameterization at the database level: It will not happen if your SQL statements contain any of these: Simple Parameterization has a number of limitations in SQL Server.
Today I want to continue this discussion by talking about Forced Parameterization in SQL Server. A few months ago I blogged about the challenges of Simple Parameterization in SQL Server.
0 kommentar(er)
