I have a MS2012 server running MS SQL 2012 web edition. I'm just wondering about the size of the database transaction logs on my DNN sites. They range from 400MB up to about 1.5 GB. Is this normal? It seems that the log files are not being backed up and therefore not being truncated. The actual databases are backed up daily via plesk panel and the server as a whole is backed up daily. Databases are all in FULL backup mode. I read that switching to SIMPLE mode should help to keep the log file size down to a minimum. I'm not sure if I should switch the database backup mode to SIMPLE or not.

Any thoughts or ideas on how to manage this better would be greatly welcome.

Yeah I'm thinking I'll do the same, I really need to be able to restore from a previous plesk backup if needed so I'm guessing switching to simple will be OK and I'd still be able to do this?

Just to be clear: switching backup model to simple means, that not all changes are added to transaction log to be able to restore not just last backup but redo all changes just until the latest action (given there is no hardware crash affecting the transaction log as well, therefore TLog is stored on separate disk in critical production situations.
Websites with little changes will mainly loose a day of logs and maybe a few user comments, if you don't care too much about loosing this, you should be fine with simple recovery.

You don't necessarily have to do a backup just to switch the recovery model and you may also notice a slight performance increase, as changes don't need to be written twice afterwards.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN