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 |
|
Joekos
Starting Member
3 Posts |
 Posted - 2013-06-18 : 09:46:55
|
| We do a full backup of several databases every night (Recovery Model: Full) Using the above backup schedule how often should the transaction log be backed up(standard practice)?Also can the ldf be shrunk with this backup model? We have one ldf that is very large, several times the size of the actual dB and we'd like to shrink it. |
|
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2013-06-18 : 10:07:46
|
quote:
Originally posted by Joekos
We do a full backup of several databases every night (Recovery Model: Full) Using the above backup schedule how often should the transaction log be backed up(standard practice)?Also can the ldf be shrunk with this backup model? We have one ldf that is very large, several times the size of the actual dB and we'd like to shrink it.
If you don't back up the log file, it never shrinks - it will keep on growing.So the first thing you need to do is a log backup. Once you do that, you will see that there is lot of free space in the log file. You can then shrink it to some "reasonable" size.Going forward, do regular transaction log backups. How frequently you should back up depends on how fast the log file grows, how much disk space you can tolerate for the log file, whether you have other recovery plans in case of disaster etc.I would start with log backup at 1 hour intervals and see how it goes.Some of the discussion in this thread might be useful to you: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=184711 |
 |
|
|
Joekos
Starting Member
3 Posts |
Posted - 2013-06-18 : 10:49:02
|
| Thank you for your help. I'll use your thoughts and also check out the thread. |
|
|
|
|
|
|
backups-transaction logs