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 |
ejbatu
Starting Member
21 Posts |
Posted - 2010-09-30 : 12:36:02
|
Hi,What is the best way managing tlog from growing so large during/after a weekly maintenance? 1. - Is it to set the recovery mode to simple - do reorganize index - rebuild index - update stat - set recovery mode to full - shrink tlog file - do a full backup 2. Do a more frequent backup on the tlog file (maybe every 20mins) - do reorganize index - rebuild index - update statIf you have a better way of doing managing, please share |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-09-30 : 13:33:58
|
1. Switch to SIMPLE recovery model. That's it. Perform a full backup daily/weekly, whatever you require. Never shrink the database files except on a one-off. Update stats/index rebuilds/reorganizes are not related to managing the tlog. 2. Use FULL recovery model, backup the tlog every 15 minutes, full backup daily/weekly, whatever you require. Add in diffs too if you'd like. Again update stats and index stuff is not related to managing the tlog size.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
ejbatu
Starting Member
21 Posts |
Posted - 2010-09-30 : 13:43:13
|
Tara thanks for the reply.What do you mean by: quote: Update stats/index rebuilds/reorganizes are not related to managing the tlog.
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
ejbatu
Starting Member
21 Posts |
Posted - 2010-10-01 : 10:45:00
|
What is an acceptable size of a t-log file?Also if you don't mind sharing, what your current production DB data size and t-log size? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|