Magnus Hagander wrote:
> I would guess they're referring to the ability to "pin" a table into
> memory, so that it always stays in the cache regardless of what else the
> database is doing. There is a narrow use-case where this can be very
> useful, but it can also be a very dangerous tool (hint: if you pin a
> table that grows up to say 80-90% of your RAM size, your database will
> not be fast for anything else)
I know that MS removed this ability in SQL Server 2005 for pretty much
this reason; it's usefulness was greatly outweighed by people screwing
up their systems by not calculating things correctly.
