Hi
This is for guidance only, and before taking this recommendation make sure that
1. You don’t need to “wind back” on your database / site
2. You don't need to perform a restore newer than the last backup
3. You hosting company support it.
SQL like all good databases provides the option to make transaction logs. This is very powerful if you are developing a system and need to be able to go through the logs in order to debug it.
Or your system crashes and you need to restore to the moment before it crashed.
The latter might be the case if you take on-line orders and haven’t pulled them from the site to your in-house system, but I’m sure you have the orders emailed in as a backup, and the site crashes completely
You can get your hosting company to change the Recovery Model to Simple
This dramatically reduces the growth of the transaction log, and you can normally truncate it very infrequently
Iowa Computer Gurus also have an excellent SQL Schedule Module – which keeps some tables in check