Transaction Log Backup Too Big
-
Hi Guys I hope someone will be able to give me advice on this. Our client have a service that trancates a particular table every 30 minutes. Then it re-inserts information into this table, run update statements to update certain fields with values from formulas. The problem is that now there is quite a number of unnecessary transactions in the transaction log. This results into the backup (with the trancate option) file to be about almost 20GB (I know!!!!) per day. So, my question: Is there any way possible that I can exclude this particular table's transactions from being logged? Could someone maybe give me advice on how I can get this transaction log file size smaller. Your help will be greatly appreciated. Elizma
-
Hi Guys I hope someone will be able to give me advice on this. Our client have a service that trancates a particular table every 30 minutes. Then it re-inserts information into this table, run update statements to update certain fields with values from formulas. The problem is that now there is quite a number of unnecessary transactions in the transaction log. This results into the backup (with the trancate option) file to be about almost 20GB (I know!!!!) per day. So, my question: Is there any way possible that I can exclude this particular table's transactions from being logged? Could someone maybe give me advice on how I can get this transaction log file size smaller. Your help will be greatly appreciated. Elizma
You can shrink the logfile on demand. There's help on how to do that from the Management Studio here[^], or if you want to do this from SQL, look here[^]. That will only help until the file fills up again, or you'll have to hunt down the reason why the logfile is filling up. The documentation on the transaction log can be found here[^]. Good luck :)
I are troll :)