2012-09-03
2,488 reads
2012-09-03
2,488 reads
2012-07-27
3,018 reads
2012-07-04
1,443 reads
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.
2012-06-14
2,481 reads
2012-05-18
76 reads
We have a new forum setup for your Powerpivot questions. If you are working with Powerpivot, please feel free to ask questions here.
2011-11-16
1,895 reads
The SQLServerCentral 2011 Party at the Summit is getting bigger and bigger. See if you are on the list, and if not, learn how to get your ticket.
2011-10-11 (first published: 2011-10-05)
998 reads
Help us collect some data on the sizes and counts of databases in your environment. Take a few minutes and answer this survey.
2011-07-18 (first published: 2011-07-01)
3,219 reads
2011-06-25
3,328 reads
2011-06-22
51 reads
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
By DataOnWheels
I have been active in the data community throughout my career. I have met...
By Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
hi, in an ssis for each loop over an object variable called MyListVariable, i...
SQL Server is typically viewed as a transactional or analytical database engine. However, it...
On SQL Server 2025, when I run this, what is returned?
SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL') See possible answers