September 10, 2014 at 8:33 pm
Hi,
We have configured log shipping for SharePoint content databases in SQL Server 2008 R2 SP2.
In Primary, the database size was 5 GB and free space was 4 GB. I did shrink the data file and made it 500 MB.
But on Secondary, the data file size is still showing 5 GB. It should show 500 MB right?
Ideally, when we shrink the data file on Primary, data file on secondary also should shrink after restoring the log backup that occurred after shrink operation right?
Please advice what to do in order to shrink data file on secondary to reflect same as size as Primary?
September 11, 2014 at 8:23 am
You're right, the log should shrink. Are you sure the log backups have been successfully restore to the secondary database? What information is in the [<secondary_Server>].msdb.dbo.log_shipping_monitor_history_detail table about the status of the logs being restored?
September 12, 2014 at 10:10 am
yes, log backups are successfully applied every 15 mins and they are in sync.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply