March 31, 2006 at 6:52 am
Hi all,
Heres a question I would appreciate some explaniation on:
I have a log shipped database (full recovery mode, trans logs every hour).
the Log portion of the DB continues to grow as it is in FULL mode.
If I do the following to shrink the DB log
TRUNCATE the log (backup log what truncate_only)- empty inactive transactions from the transaction log file.
and then
SHRINKFILE on the log - physically reduce the size of the transaction log file.
would that affect the transaction log backups as it advised to do a complete backup after that. I am particularly concerned that this may affect the log-shipping. Any answer with the supporting theory behind this will be gratefully recieved.
P.S I have found that generally I can get away with doing a shrinkfile only and this reduces the log without messing up the log-shipping.
Siz
March 31, 2006 at 7:57 am
you can /may reduce the size of the file on a log shipped database.
Generally though if there are pending transactions it will not shrink very much unless you force a page reorganization.
But if you shrink file right after the log is shipped you can just truncate it, and you should have no problems.
March 31, 2006 at 8:39 am
Excellent, thanks Ray.
"Generally though if there are pending transactions it will not shrink very much unless you force a page reorganization"
By this do you mean running the Microsoft supplied script (transaction wraparound) that forces all active/pending transactions to the top of a log file thus freeing up space at the end to allow you to shrink the log? If YES then does this affect the Log-shipping?
March 31, 2006 at 8:41 am
Any manual Log backup *may* break logshipping. be careful.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply