March 10, 2008 at 3:53 pm
I have log shipping going to a dr site (older server). When I rebuilt indexes on the largest db, the ldf file grew to large for the dr server. On a smaller db in the log shipping I de-attached and re-attached the db mving the ldf to another file. It blew up the log shippping, when re-attaching it set the db from read-only to normal Any way to do this without losing the read-only status?
March 10, 2008 at 4:12 pm
this option should work -
for the smaller db re-initialise log shipping by restoring full backup from the primary, when you restore with standby or norecovery also specify with move option to restore ldf to new directory, then continue as normal
---------------------------------------------------------------------
March 10, 2008 at 4:16 pm
I was aware of that route and had done this before. Problem is we are talking 28 gig across a T1 line
March 10, 2008 at 4:38 pm
ah, thats a shame, I don't think there is any other way. Unfortunately I guess your log chain is broken so you have no choice but to re-initialise...............
---------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply