AWE – Lock pages in Memory query | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

AWE – Lock pages in Memory query

Why if you enable the ‘lock pages in memory’ option and don’t enable AWE, can you incur a performacne problem? Is this because you might lock too many pages in memory for SQL Server processes which will never be released, and consequenlty there will not be enough memeory for the operating system?
AWE not needed in 64-bit version of OS and SQL Server 64-bit edition,In 32-bit version you have to define AWE and lock pages ,if you define lock pages enable for the specific user account and you did not enable AWE then SQL Server will not gain memory If you don’t enable lock pages for the specific user and anti-virus is running on the OS then OS understand that is a virus and process is going crash or drop
Sorry that doesn’t answer the question. Why might you get performance problem when you enable lock pages in memory and dont setup awe?
Becuase when SQL Server need more RAM then it cant ,Page life will be suffer and physical IOs increase ,your SQL Server Service account must have lock pages rights on the running OS
]]>

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |