We are working on converting to SQL 2005 database. During the conversion we are having to rewrite a lot of code and doing a lot of intital testing and development on development data. This is causing our transaction logs to really big. I have created a maint plan that runs nightly that does a back up of database and tran log but throughtout the day the tran logs are getting really big and eating up a ton of disk space. Does anyone have suggestions on what sort of maint plan I can setup to run on my developement data where as at this point I am not concened about being able to roll back the database just keep is small as possible and "healthly"
All ideas are appreciated
Thanks
Chris
Hi,
If your database has recovery model set to FULL you can schedule to take a T-Log backup on half/hourly to keep it in shape.
BTW are you doing Re-Indexing / Bulk Insertion-Updation !!!
Hemantgiri S. Goswami
|||Would you recommend running the hourly t-log backups by creating a maint plan?
I have a maint plan running nightly that is perfoming reindexing, update stats, and shrink the db. We are also converting in data via text files and bulk inserting but when we do this we are shutting off as much of the logging as possible.
Would you happen to know of any articles, white papers or anything like that I could read up on?
Thanks for your time.
Chris
|||Hi,
As you said that you have a maint plann running nightly which does ReIndexing... Re Indexing actually keep your T-Log file growing, what is a plan you have for shrinking!!! Refer http://hemantgirisgoswami.blogspot.com/2006/03/cause-for-t-log-become-full-and-how-to.html
Regards
Hemantgiri S. Goswami
|||Thanks for the suggestions. The articles are very helpfull.
