Symptoms
You observe that Server.Log table keep growing constantly, its size never goes down and keeps increasing.
Diagnoses
Under normal conditions Server.Log table as it has to be constantly processed by K2 logging threads (in default configuration there are 20 of them) and data is moved out of this table to other *.Log tables.
In case your Server.Log table keep growing and never becomes empty over prolonged period of time then it is sure sign of issue with your processes or specific process instances which for some reason cannot be processed by logging threads or generate abnormally high volume of logging data.
Server.Log table will not shrink when archiving/using built in stored procedure, as Log entries in this table still needs to be moved to the K2ServerLog schema so in essence your logging is either stuck or processing was extremely slow.
The following can be recommended in such case:
1) Please monitor your Server.Log table and confirm that it is not keep growing again. Normally it should be empty for most of the time/entries should be moved out of it at least slowly. If this is not the case I think we will need your DB to investigate what exactly is wrong/do a cleanup.
Please check this. If your log processing is stuck you may also have a couple of Log server related errors when K2 server is started up in K2 host server log.
2) It maybe the case that there is some problematic entry/entries from Server.Log which has to be cleared up in the database (please contact K2 support to get an assistance with this).
3) If your Server.Log table is being processed normally you may still want to put some monitoring checking table sizes and if necessary trigger log archiving. In theory you can automate this with some scripting.
Point (3) is especially valid for SQL Server Express which has hard database file size limits. To check on SQL Express limits you can use something like this: http://selectstatements.blogspot.ru/2013/01/check-database-size-against-sql-server.html
Resolution
Based on experience such growth of Server.Log table can mostly be caused by some issue with your processes (e.g. bugs/orphaned items in the item reference logserver) or issues with log processing. It is recommended to engage with K2 support to get assistance in such scenario.
