November 4, 2024 at 4:04 am
Dear All,
We have been facing this issue from last 3 months and unable to conclude a solution. Request your inputs please...
The production server is running with SQL 2022 with Always On. Once a week, the CPU is consistently above 85%, which hung the system. We noted the long-running queries/jobs and blocking queries and fine-tuned them. Even after this, we faced the same issue after a week. We increased the CPU from 8 to 16, RAM from 256 to 512 GB. Again we faced the same issue after 10 days of upgrade. This time we stopped the SQL Agent and we even killed the open transactions to see whether the CPU % is coming down. Still no luck and the CPU remains at 85 -90% utilization. Once we restart the services everything goes fine. Can someone help me to figure out this issue please? Thanks in advance1
SQL version : Microsoft SQL Server 2022 (RTM-CU10) (KB5031778) - 16.0.4095.4 (X64) Oct 30 2023
Chella
November 4, 2024 at 4:33 am
How many different dbs do you have? Do you get any "insufficient threads" messages? AO uses threads quite a bit.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
November 4, 2024 at 4:57 am
We have around 40 databases in this server. We didn't face insufficient thread messages.
November 4, 2024 at 5:10 pm
Since we don't have much info on your setup, this is a stab in the dark:
1. Are you in a virtual environment? Is it shared? could be a noisy neighbor issue.
2. How different are your SQL Server waitstats during the time of the issue as compared to normal time periods. What are your greatest waits?
3. Any other apps on the server that might be causing the issue?
4. What are your batch requests per/sec? If you have a very high concurrent workload, then it is possible it might be a spinlock issue.
5. Were there any changes to the app or server prior to the issue appearing?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply