January 9, 2010 at 9:30 am
I have a gut feeling that we really don't need Full recovery model. Now,I would like to take the full backup followed by log backup and then change the recovery model to simple. Do you suggest this or is there any other way to change full to simple.
Thanks
Ali
January 9, 2010 at 9:35 am
Hey Jeff,
I am really sorry and I am really thankful to you. I never thought of being arrogant. I was really in urgency to know what's going on in my database.
!!Sorry for the arrogant message though!!
Thanks for your message Jeff. I did'nt see your second message before posting my messages. I really thank you for your suggestions.
Thanks
Ali
January 9, 2010 at 11:26 am
I have changed my recovery model to simple, took a full backup of my database, shrunk the database, ran rebuild and update stats. I recovered my space. i don't need to add any space now.
Thank you so much guys. You guys helped me a lot. :):)
Thanks
Ali
January 10, 2010 at 11:21 pm
If you do not have a policy of log backups, then it is advisable to sqitch to simple recovery model. This would not need any sort of log maintenance from your side.
This should only be done after management review.
This will help you reduce your log file size to less than half, but be sure to set the file growth to an appropriate number to support heavy transactions.
Akhil
December 7, 2016 at 7:47 am
To fix T-log full issue during rebuild index maintenance task/ job, find out which indexes causes to Full t log file and exclude these indexes from Rebuild index maintenance plan or script/sp which you are using to rebuild/reorganize index job, If indexes are really required and must be rebuild to achieve performance, then create Partition on the table on which index is created and rebuild index only on last partition.
December 8, 2016 at 4:59 am
Ah, sorry , ignore....
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply