SQL Server Central

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,509 reads

Blogs

Monday Monitor Tips: Configuring Access to the MCP Server

By

I have been experimenting with MCP servers in a few ways, including the Redgate...

The GO Barrier: Why SSMS Multi-Server Query Waits for the Slowest Connection

By

I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...

10 Things I Hate About Fabric Deployment Pipelines— And Some Alternatives

By

Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...

Read the latest Blogs

Forums

A Challenge of Our Knowledge

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Challenge of Our Knowledge

The memory toll of VARCHAR(MAX) in SQL Server

By sabyda

Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...

Transaction Log Truncation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Transaction Log Truncation

Visit the forum

Question of the Day

Transaction Log Truncation

In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?

See possible answers