Client discovers an increase in transaction log size and is running out of space on the drive.


Maintenance of the SQL server and Log files Maintenance are usually handled by IT persons managing the infrastructure. This could be a clients in-house or external IT staff. These log files are different to the application logs generated by ClickHome3. Regular back up of the transaction log eliminates growth. Each time the log is backed-up, it resets the internal use of the log, and the new logs just overwrite.
The easiest way to recover the space used by the transaction log is to set the database recover mode from full to simple and then do a normal backup. We recommend a full database backup before changing the recovery mode. You should now be able to put it back to full recover mode and then using regular log file backups, the log size will stay under control.

Use of temporary tables in queries may use more log file space. However, if you do not want to have a log file which gives you the ability to recover the database to a point in time, then you can choose Simple recover mode. If you do want the ability to recover to a point in time, then you need to consider how you backup and manage the transaction logs with Full recovery mode. Some of our clients with suitable disk drive and server redundancy choose to use Simple recovery mode and we have done so for quite a while without trouble.

Some Suggested Links on Backup methodology are below:

MSDN Overarching Backup Article:
SQL Authority Blog:

Other Links