October 15, 2009 at 9:01 pm
I have a job that run weekly that does the re indexing of the database, but this job causes the log shipping process to fall out of sync. Do I have to disable the log shipping job on following servers?
- disable logshipping job on monitor server
-disable copy logshipping on destination server
-disable the log back up on destination and source server
Please help me which job to disable before reindexing- Do we even need to disable?
Or should I reindex in small chunks with running log shipping?
October 16, 2009 at 11:41 am
How often do you log ship?
Depending on your db size and table size you should reindex in small chunks.
You can also set log shipping to execute every 5 mins during reindexing of huge tables that way log on secondary will be applied in chunks.
October 16, 2009 at 11:54 am
How are you rebuilding your indexes? If you're using the database maintenance wizard, it will blindly rebuild indexes whether they need to be rebuilt or not. If that's the case, then I'd recommend implementing a smart index rebuild script. I've modified the one written by Andrew Kelley that was published in SQL Server Magazine.
You can find others from Kimberly Tripps blog here:
I worked for a client who was using the index maintenance wizard and rebuilding the indexes on a huge table that generated 90 GB of logging and the indexes weren't even fragemented. We implemented this solution and they no longer had the issues with log shipping getting out of synch.
October 18, 2009 at 11:08 pm
My 2 cents...
Using a smart script will definitely reduce the problem but may not completely solve it. Certain indexes will still be fragmented and require a index rebuild. This may not happen often but will still occur.
"Keep Trying"
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply