I have a similar question to this: https://teamcity-support.jetbrains.com/hc/en-us/community/posts/115000571390-TeamCity-heartbeat-putting-load-on-sql-server?input_string=Team%20City%20has%20slow%20builds%20possibly%20caused%20by%20heavy%20SQL%20Server%20usage
We seem to have builds whose duration varies significantly between 18 minutes and 30 minutes. When the build is slow, the only obvious thing that is running heavy on the TeamCity server is the database, taking up an entire core and possibly then pegged, which might well slow everything else down. When I run the SQL profiler, it doesn't seem like lots of important traffic, more like thousands of progress type calls, some of which don't even look like complete statements.
I guess my questions are:
- How I can debug this high cpu usage for SQL Server?
- Is there any way I can run something to check/clean up the database?
- Since we have upgraded many times, is it possible the database is messed up and can it be reset?