SQLServerCentral

SQLServerCentral Article

SSC Clinic: Can Implementing "Optimize for Ad Hoc Queries" Boost Performance for the SQLServerCentral.com and Simple-Talk.Com SQL Servers?

  • Article

With the introduction of the instance-level option “optimize for ad hoc workloads” in SQL Server 2008, DBAs have a tool to deal with a problem known as plan cache pollution, or plan cache bloat. It’s often caused when one-time use ad hoc queries are sent to SQL Server from Object-Relational Mapping (ORM) solutions, such as LINQ, NHibernate, or Entity Framework. The problem can prevent SQL Server from using its available memory optimally, potentially hurting performance.

(10)

You rated this post out of 5. Change rating

2012-06-14

2,479 reads

Blogs

Advice I Like: Ranch Rules

By

Leave a gate behind you the way you first found it. – from Excellent...

Fix Slow, Bloated MSDB: Purge Old History And Add Missing Indexes

By

Fix Slow, Bloated MSDB: Purge Old History And Add Missing Indexes ...

Three Ways to Use Snowflake Data in Microsoft Fabric

By

Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...

Read the latest Blogs

Forums

Automating Database Cleanup for PostgreSQL Using Python

By sabyda

Comments posted to this topic are about the item Automating Database Cleanup for PostgreSQL...

The Query Optimizer and Page Density

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Query Optimizer and Page...

There Are a Lot of Databases

By Steve Jones - SSC Editor

Comments posted to this topic are about the item There Are a Lot of...

Visit the forum

Question of the Day

The Query Optimizer and Page Density

If I have a fillfactor set to 70%, this reduces my page density to roughly 70%. Does this affect the query plans that the optimizer chooses?

See possible answers