TheSQLGuru (6/2/2009)

---

1) I am curious what among these listed reasons where why you chose to do forced parameterization for your database. See here in BOL:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/068282b7-c419-4e2c-990a-1f8b7c12762f.htm

I do have a client with a metric butt-ton of really horrible looping ADOc code and we picked up 30-35% throughput gains with forced parameterization.

2) doesn't make a difference on my copy (sql 2005 sp2):

use master

go

alter database AdventureWorks set PARAMETERIZATION FORCED

go

use adventureworks

go

dbcc freeproccache

go

exec test2 @productid = 790

use master

go

alter database AdventureWorks set PARAMETERIZATION SIMPLE

go