Forum Discussion
SharePoint SQL Server at 100% CPU Utilization
- Nov 11, 2020
SteveUpchurch I don't think anything is "wrong", per se. It's just an expensive query (indeed this had pref problems as recently as this year in SPO). As to what exactly is generating the query, I'd have to go sproc hunting 🙂
Curious to know if you've applied any patches recently and/or if you're at the Nov 2020 CU level, yet.
Trevor Seward Thanks for the reply! I absolutely agree that it sounds like navigation. We use the term store terms to define the structure for global navigation at the site collection level and inherit it at all sites below that. We don't do dynamic metadata navigation based on site or library.
Are you thinking that the query is generated when a user is using site navigation? Like maybe something in the nav structure is screwed up and needs to be rebuilt?
Thanks!
- Nov 11, 2020
SteveUpchurch I don't think anything is "wrong", per se. It's just an expensive query (indeed this had pref problems as recently as this year in SPO). As to what exactly is generating the query, I'd have to go sproc hunting 🙂
Curious to know if you've applied any patches recently and/or if you're at the Nov 2020 CU level, yet.
- SteveUpchurchNov 16, 2020Copper Contributor
Trevor SewardThanks, Trevor. I am not yet at the November 2020 CU level. Perhaps that will provide some different results. I understand what you are saying about it being an expensive query. While we have been using the same navigation method for several years, the CPU utilization problem has only started occurring more recently, like within the past 2 to 3 months, and then only sporadically. I have been unable to find a pattern or a trigger.
I will apply the Nov 2020 CU and see if that helps. In addition, I am in the process of migrating the environment to on-premise SP 2019 and I might re-think the way navigation is handled in the new environment.
- Nov 16, 2020If you move to the modern UI, yes you'll have to re-do navigation entirely since it no longer uses metadata-driven navigation. But of course you can stick with the classic UI and continue to use metadata-driven navigation.