July 23, 2012 at 6:49 am
Hi,
for some massive transactions, if my LDF file grows very large and while checking using the query : sp_replcmd I can see a huge list of queries are marked for replication, what are the precautionary actions I can take to restrict the growth of the Log files...since I can't change the recovery model of the database and also I can execute sp_browsecmd or sp_repldone.
Please suggest some of the best practice in such scenarios!
Thanks.
July 23, 2012 at 2:50 pm
If the database is in full recovery model then make sure you take regular backups. That is the best way to keep the log file size in check. If you don't take regular backups then the log file size will start increasing. I would schedule the log backup to run every 15 minutes and see how large the backup files are. If they are not large then you can reduce the frequency to 30 mins and then later 60 mins.
It all depends on the amount of transactions. The best way to check that is to schedule frequent log backups and see how it goes....
If it is in simple recovery there is not much you can do with the log file size. It will keep growing depending on the amount of uncommitted transactions.
Blog
http://saveadba.blogspot.com/
July 23, 2012 at 10:00 pm
Ofcourse regular log backups are scheduled.
Question to this context is, if there are massive transactions are running at publisher end and the LDF file is growing what is the best way to deal with it!!!
Thanks.
July 23, 2012 at 11:02 pm
A very large transaction will cause the log to grow. There isn't anything you can do to 'deal with it' apart from ensure you have sized the transaction log appropriately to prevent any (or excessive) autogrowth.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply