Why is sql server 2016 loading cpu at 100%?

Question

1C-Enterprise

The situation is as follows: there
was a server with win 2012r2 32GB of RAM, sql 2008 - reinstalled the axis on win srv 2016, added another 32 gigabytes of RAM, installed sql server 2016.
When installing sql server, the default parameters were changed, which later played a cruel joke - when users were working in 1s - the database got up - deadlocks started, users were reset .. I
tried to remove sql server and reinstall it by attaching the databases (without backup and restore) - but it didn’t get better ..
Who can poke where to dig, all local " "experts" were already involved - no one could help.
my knowledge in sql server is minimal :(

Answer 1

the problem was that the backup turned out to be broken, restored again - and it worked fine

Answer 2

adding bases

Set the database compatibility level to 130 ("Properties", "Options").
Use the Profiler application (included in the package) to determine server load requests.
Let's assume that MS SQL is in vain due to the lack of a DBA.
Try to get started: how to set up MS SQL to work with 1C .

what can cause such an I/O flow in sql ?

1C. It does not use SQL server optimization at all.
You can try rebuilding the indexes.
Reorganization and rebuilding of indexes .

Answer 3

Turn off multithreading in the whine-advance settings and set the max dop property to 1, and always one request will consume only one thread, and sometimes not request 8 or more threads, loading the CPU to the maximum