Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MetroGuy
Starting Member
1 Post |
 Posted - 2004-11-08 : 16:54:38
|
| I do a full backup on my user databases once a day in the evening, with recovery set to full. In the AM after all our collected raw data is in from the field (from Pocket PC devices) and some processes are run, I do a transaction log backup. I'm sure you can guess my question is about the size of the transaction log file. Sometimes it can double in size, especially over the weekend. When this happens, I set the recovery mode to simple and shrink the database which recovers the empty space in the log file, then reset to full recovery. Is this wise? It doesn't seem to cause any problems.I'm considering permanently changing recovery mode to simple and doing a differential backup in the AM. Would this keep my log file size under control? I know I'd lose some flexibility on a restore, but I can probably live with that. I also run an optimization process once a week on Sunday eves. Could that be running up my log file size? |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2004-11-08 : 17:20:52
|
| That should keep it under control. The optimizations usually include rebuilding your indexes which causes a lot of transation logging. You will lose the ability to restore to a point in time if you switch to simple. If you can live with that, then go for it.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
|
|
|
TR Log vs Diff Backups