WID Database Page Error Event 17890 - Since January 2021 update

Steve Babcock 21 Reputation points
2021-01-25T16:19:53.757+00:00

I have noted the following entries in the Application Log since the January 2021 update
I manage a bunch of RDS server and they all show the same

Event 17890
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1520 seconds. Working set (KB): 152332, committed (KB): 369624, memory utilization: 41%%.

While this is just an Informational message, the CPU for SQL is now in the 10-12% consitently and is causing RDS performance issues

Is there a way to manage the WID memory and fix this ?
But, the CPU for SQL is now high as well and causing RDS performance issues

Steve

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,305 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Karlie Weng 15,196 Reputation points Microsoft Vendor
    2021-01-26T06:54:07.853+00:00

    Hello @Steve Babcock

    "SQL Server monitors the various memories related information about the SQL Server process. In this case, it has detected that the working set of the process is less than 50% of the committed process memory. As a result this warning is printed. The normal causes of this warning are:

    • The operating system pages out large portions of the SQL Server committed memory to the paging file.
    • This could be due to sudden increased demand for memory from other applications or operating system needs.
    • This could also happen when certain device drivers request contiguous memory allocations for their needs."

    Quoted from MSSQLSERVER_17890

    Best Regards
    Karlie

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments