Skip to content
  • There are no suggestions because the search field is empty.

Why do SQL Server logs show “A significant part of SQL Server process memory has been paged out”?

Learn why SQL Server reports memory paging and how limited RAM or settings can slow down Acctivate.

Acctivate users may notice the following message in the SQL Server Error Log:

“A significant part of sql server process memory has been paged out. This may result in a performance degradation.”
Duration: 1243 seconds
Working set (KB): 80068
Committed (KB): 437448
Memory utilization: 18%

This message occurs when Windows pages SQL Server memory to disk instead of keeping it in RAM. One common cause is that the server has limited available RAM resources, especially if multiple applications are running, if the server is under heavy load, or if SQL Server is not configured correctly.

Expected Result

SQL Server should keep its allocated memory in physical RAM for stable, fast Acctivate performance.

Actual Result

Windows moves part of SQL Server’s memory to the page file, causing performance issues such as slow posting, delays in synchronization, sluggish reports, or general Acctivate slowdowns.

Steps to Resolve

1. Confirm the server has adequate RAM

A frequent cause of this message is insufficient RAM.

  • If the server is regularly reaching high memory usage, consider adding RAM.

2. Set SQL Server Max Memory

If SQL Server uses too much memory, Windows may page it out.

  1. Open SQL Server Management Studio (SSMS).

  2. Right-click the server name → Properties → Memory.

  3. Set Max Server Memory to a level that leaves RAM available for Windows and other applications.

    • Example: On a 16 GB server, set Max Memory between 8–12 GB.

  4. Click OK.

3. Enable “Lock Pages in Memory”

This prevents Windows from paging SQL Server memory to disk.

  1. Open Local Security Policy (secpol.msc).

  2. Go to Local Policies → User Rights Assignment.

  3. Select Lock pages in memory.

  4. Add the SQL Server service account.

  5. Restart the SQL Server service.

4. Check for Windows memory pressure

Limited RAM combined with other processes can force paging.

  • Verify antivirus exclusions for SQL and Acctivate folders.

  • Close unnecessary applications or server roles.

  • Ensure no other services are using excessive memory.

5. Review Windows virtual memory settings

Ensure the page file is managed properly and stored on a healthy drive.

6. Monitor for further paging alerts

Use SQL Server Logs in SSMS to check if the paging message reappears.