Ola dbcc checkdb causing huge spike in memory usage. #947
Unanswered
absevolutionapps-cmyk
asked this question in
Questions & Answers
Replies: 1 comment 1 reply
-
It sounds like this is related to the DBCC CHECKDB command itself, rather than the DatabaseIntegrityCheck stored procedure. Could you try installing the latest cumulative update package for SQL Server 2022? Or open a support case with Microsoft? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have been using Ola maintenace script for several years now, but just here recently we have noticed that on fairly large databases (50GB or more) that the checkdb job is causing large spikes in memory usage on our servers. The usage can go from 10GB to 50GB after the job runs, then of course SQL doesnt let go of that memory until a server reboot. For the time being we have limited the memory usage that SQL can grab, but was wanting to see if anyone else has ran into this issue here recently.
Here are the specs of our server and SQL Server versions:
OS - Windows Server 2025 Standard
SQL - Microsoft SQL Server 2022 (RTM-GDR) (KB5058712) - 16.0.1140.6 (X64) Jun 19 2025 11:40:25 Copyright (C) 2022 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2025 Standard 10.0 (Build 26100: ) (Hypervisor)
Version of Ola's Script - 2025-06-09 16:43:17
Beta Was this translation helpful? Give feedback.
All reactions