December 2, 2018 at 5:11 am
Hello
Bit of a silly question I think, but for my peace of mind...............…
We have 2 servers - Live and Reporting, and use Transaction Log Shipping to update Reporting.
If I do maintenance on LIve (or Reporting) to truncate the logs and reduce VLFs, do I need to
keep the changes in Sync -i.e. do the Log structures at each end need to look the same?
Logically not, but I don't want to screw anything up - just thinking to make a change on Reporting
first before Live.
Fyi - I spotted the new eBook by Tony and Gail and will start to work through it in case anybody
suggests that.
Regards
Steve O.
December 2, 2018 at 10:03 am
I don't think you will be able to change that on the reporting system - to do so you would have to bring the database online first. If you are looking at optimizing the transaction log - I think it will have to be done in production and then you would have to backup production and restore to reporting and restart log shipping.
If you are attempting to truncate the logs by switching to SIMPLE, shrinking the log and rebuilding it at appropriate size increments - that also cannot be done without breaking the log shipping process. Note: it isn't necessary either...
To reduce the log file size - shrink the file - backup the transaction log - then shrink again until you are down to the size you want. Make sure you set the auto-growth size to the size you want before shrinking - that way if a growth is required during the process it will grow it out at the size you want.
And as stated before - once you have this completed in production - then you can restore to reporting and rebuild log shipping.
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply