Again with this question. 🙂
I've got a log-shipped database, and I would like to decrease the size of the transaction log.
What's different from the other examples of this question I've seen here is that I do know that the current size of the transaction log was caused by a single large transaction which will not be repeated any time soon.
So as I said: I would like to get my TLog back to the 30 GB it's been for the last 6 years or so, instead of the 240GB it is now.
Can I safely use the 'truncateonly' option on the transactionlog (without killing the log-shipping)?
In all examples of this question there have been comments about not shinking the log except in case of exceptional transactions, but I've yet to see a clear go/nogo response if the issue _is_ known to be caused by an exceptional transaction.
- This topic was modified 1 month, 3 weeks ago by mavelzen.