Search This Blog

Sunday, March 21, 2010

Using Locked Pages for SQL Server 2008

Select * from sys.dm_os_process_memory

gives us Information on locked pages.
How does that help? Locked pages can improve SQL Performance to an extent and afterall SQL is backend for SharePoint.

Here is very good article on AWE/PAE and other switches

http://blogs.msdn.com/psssql/archive/2009/09/11/fun-with-locked-pages-awe-task-manager-and-the-working-set.aspx

http://msdn.microsoft.com/en-us/library/ms190673.aspx

http://blogs.msdn.com/chadboyd/archive/2007/03/24/pae-and-3gb-and-awe-oh-my.aspx

http://blogs.technet.com/beatrice/archive/2008/08/29/3gb-pae-and-awe-taking-away-some-confusion.aspx
Here is an excerpt from the above blog:
Now then, so why considering x64 Architecture if we have AWE?
The use of SQL Server (32-bit) with AWE has several important limitations. The additional memory addressability is available only to the relational database engine’s management of database page buffers. It is not available to other memory consuming database operations such as caching query plans, sorting, indexing, joins, or for storing user connection information. It is also not available on other engines such as Analysis Services.
For more detailed information, refer to:
Advantages of a 64-bit Environment
http://www.microsoft.com/sql/techinfo/whitepapers/advantages-64bit-environment.mspx






SQL 2005:
DBCC Memorystatus

No comments: