July 18, 2011 at 11:52 am
Long running transaction on a large database, underestimated the required size needed for the log file, hit the drive limit before I could add a second log file. It will now rollback all transactions as if I had cancelled the query, correct?
July 18, 2011 at 11:54 am
Yes.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 18, 2011 at 2:18 pm
And - there are no shortcuts. You will have to wait for it to complete the rollback.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 18, 2011 at 2:21 pm
yeah, i figured that part out. i thought i'd caught it and added a second t-log in time, but apparently not...just realized this morning that the number of null columns in a table was going up instead of down...started putting the pieces together. </idiot>
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply