Follow

SQL transaction logs are getting very large

PROBLEM
You have found that the SQL transaction logs are quite large or larger than expected

CAUSE
Kaseya itself does not have any control over the transaction log files - SQL creates these and uses these based on its own design.

Whenever a change occurs on the database, SQL records this in the transaction logs. This allows that change, or any other change to be "rolled back" in the event of a problem.
Typically, these are used during a restore of the database.
Imagine that you took a backup of the database on Sunday night. At some point during Monday, there is a problem which leads to the database file being damaged.
Using the Sunday night backup, and the transaction log, you are able to get the database back to the last point before the failure, by "re-playing" all the transactions since the last backup.
A transaction log is only cleared once a successful backup has taken a place and when the database is set to "simple mode".

WORKAROUND / RESOLUTION
Although full details of this process is outside the scope of this KB article, in brief, to "fix" large transaction logs, you need to take a backup of the "ksubscribers" database. This will allow SQL to clear the transaction logs, however this will not automatically free up the space - that will require a shrink - see below

ADDITIONAL INFORMATION

Truncating SQL logs - http://databases.about.com/od/sqlserver/a/truncate_shrink.htm
Shrinking a transaction log that has a lot of free space - http://technet.microsoft.com/en-us/library/ms178037%28v=sql.105%29.aspx

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.