Cleanup of stale DB entries skipped

Question

Hello,

My Microsoft SQL Server error log contains very often the following line "RemoveStaleDbEntries: Cleanup of stale DB entries skipped because master db is not memory optimized.

Parallel redo is started for database 'database_y' with worker pool size [4].

Parallel redo is shutdown for database 'database_y' with worker pool size [4].

RBPEX::NotifyFileShutdown: Called for database ID: [5], file Id [0]

Starting up database 'database_y'. " where database_y has database ID: [5]

DBCC CHECKDB ('database_y')

CHECKDB found 0 allocation errors and 0 consistency errors in database 'database_y'

Do you have any idea how to continue the investigation?

Thank you.

Best regards,

Matei

Answer 1

Find pillow, sheet and blanket. Find a pyjamas. Slip in. Sleep peacefully.

Or in other words, these messages are just white noise and nothing to care about.

Answer 2

Hi，MateiG

Welcome to Mircsoft Q&A forum!

The message indicates that the cleanup task for outdated database entries was skipped due to the lack of memory-optimized configuration for the master database.

The message 'CHECKDB on database 'database_y'' indicates that no issues were found with the database, which is good news.

Therefore, the prompts mentioned are informational, and you do not need to worry.

Regards

Mikey Qiao

---

If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.