Solution : https://service.sap.com/sap/support/notes/1134345 (SAP Service marketplace login required)
Summary :
64-bit SQL Server editions prevent buffer pool paging with the "Lock pages in memory" option, ensuring it isn't paged out by Windows, which could degrade SQL Server performance. This requires granting the specific Windows account, running the SQL Server service, the privilege via "gpedit.msc" under "User Rights Assignments". For 32-bit versions using AWE to support over 4GB, SAP advocates moving to a 64-bit server. Correctly configuring the ‘max server memory’ setting is crucial, particularly when sharing the host with an SAP instance, to avoid allocating excessive memory to the SQL Server Buffer Pool.
Key words :
case sap strongly recommends, sql server error log, sql server data cache, normal windows memory management, sp_configure 'max server memory, sql server process memory, sql server configuration option, sql server service account, sql server configuration setting, sql server buffer pool
Related Notes :
| 879941 | Configuration Parameters for SQL Server 2005 |