we encountered one mysterious problem. After adding 6 more processors to our database server, from 6 to 12, we are unable to adjust the processor settings on any of the instances.
We are now running SQL Server 2019 with 12 processors. The catch is after adding more processors, SQL created another NumaNode group, but with the same name as the previous one - NumaNode0.
I assume that's why I'm getting the error below when I try to change the settings. The production environment has 5 instances.
Any suggestions on how to fix this easily?
Thanks !
**Edit:**
Output from sys.dm_os_nodes:
Output from sys.dm_os_schedulers:
And output from sys.configurations:
Any suggestions on how to fix this easily?
Thanks !
**Edit:**
Output from sys.dm_os_nodes:
Output from sys.dm_os_schedulers:
And output from sys.configurations:
Asked by Roman Schmidt
(1 rep)
Jan 29, 2024, 07:35 AM
Last activity: Jan 31, 2024, 06:14 AM
Last activity: Jan 31, 2024, 06:14 AM