Hi,
could you describe how you found out that it’s because of the compatibility level? I’ve checked and my databases are on compatibility level 130 (I never changed that manually), so you got me a bit worried, but I can’t get myself to just randomly try that on my production databases. Is there a specific scenario when this issue manifests? Are there any trace logs or performance monitor/windows performance recorder traces that could show that this is causing higher CPU usage?
↧
Comment on SP2016 – Performance Problems caused by SQL database compatibility level 130 or 140 by Piotr Siódmak
↧