July 20, 2014 at 6:57 pm
I read the following artticle from MSDN for resolving transaction log issues if it becomes full.
I am a sql server newbie, so just posting to check if these steps , especially increasing disk space will work for sql server 2008
msdn.microsoft.com/en-us/library/ms175495.aspx
July 21, 2014 at 1:19 am
Those will work..
http://msdn.microsoft.com/en-us/library/ms175495(v=sql.100).aspx
Btw, You can select which SQL Version you are using by selecting "Other Versions"
hth
July 21, 2014 at 1:27 am
Yep those steps will resolve the problem.
You will need to ask a few more questions now to the business to determine how to stop this from happening again, primarily around what is the recovery point objective (RPO), or how much data can we afford to loose before it costs the company.
That will then determine how to periodically generate a transaction log backup, to both comply with the RPO and also stops the log from getting out of control, (caveat large transactions can cause the log to grow abnormally so you will always need to keep an eye on its size).
I would also recommend this book[/url] for managing your transaction logs.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply