Summary Info
As transaction log activities do capture every Select, Insert, Delete, and Update query that is performed against the database which can be used for auditing, and can be used to restore a database to a more current state than your last backup.
However it’s possible over time for the disk space on customer's database server to eventually become over-committed by the growth of the SES Database Log file, in which could result in reaching disk space limits notably as a result of these transaction log activities. Once the disk reaches its maximum space commitment size, then what can potentially be further impacted is the ability to perform various administrative tasks through the SES console including potential impact to SDConnex or ADSync which may no longer be able to properly function. (due to disk space issues for database). At this point, until maintenance is performed to reduce the size of the database, it may not be further possible to store any new data.
With the use of SQL Management Studio product, customers can login to their SQL server and check the size of the database as well as perform the required maintenance to clean up these transaction logs. As most scenarios, it’s not the actual database file that has increased in size, but the transaction log itself. (transaction log file ends in LDF). Hence the focus of this article will be provide instructions on how to reduce the Log file size for this file.
Product version affected:
Affects all versions of SD
Environment:
Windows Servers and SQL
Propose Solution to follow:
There are 2 possible solutions for this issue:
Solution 1 (Best Solution)
Most backup software available on the market today that are capable of backing up Microsoft SQL databases are also able to truncate the log file after a full backup. Some may require you to run this as a separate job after the backup is complete.
Solution 2 (If no backup software available)
Please contact WinMagic Support in which we have scripts which can be provided to allow you to truncate the log files without doing a full backup.
You can also refer to instructions from the following Knowledge base article:
KB 1310 - How to Truncate the Transactional Log in SQL Server 2008
KB 1662 - How to Truncate the Transactional Log in SQL Server 2014