December 31, 2008 at 12:13 am
According to Microsoft BOL for SQL Server 2005, they removed the DBCC PINTABLE command.
Surely this would be useful in certain situations? Anyone have any idea why they removed this? They only have a vague statement that:
"This functionality was introduced for performance in SQL Server version 6.5. DBCC PINTABLE has highly unwanted side-effects. These include the potential to damage the buffer pool. DBCC PINTABLE is not required and has been removed to prevent additional problems. The syntax for this command still works but does not affect the server."
December 31, 2008 at 12:26 am
ta.bu.shi.da.yu (12/31/2008)
According to Microsoft BOL for SQL Server 2005, they removed the DBCC PINTABLE command.Surely this would be useful in certain situations? Anyone have any idea why they removed this?
Because people were causing problems with it. The idea was pin small tables into memory and it will speed up the system. Truth is, small tables that get frequently accessed are often in memory anyway because the pages are used often enough that they don't get flushed out.
The problem comes when people try to pin large tables into memory, severely reducing the available space in the buffer pool
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply