Search
-
Re: SCSM DB Meltdown
-
Re: SCSM DB Meltdown
And as for performance, MS recommended the following: 1. Change compatibility level to 110. We have seen this improve performance of SCSM running on SQL 2014. 2. Change DB owner to service account instead of SQL SA account. Currently, the local SA SQL account owns the SCSM DB. Since you have the database engine in Windows… -
Re: SCSM DB Meltdown
EntityChangeLog table has got to be one of the most complex topics within SCSM because so much depends on it. Brett is spot on in that it's responsible for all History of Work Items. Every change is a row in this table which means depending on how much work is happening in the system you can see a lot of activity on this…