Rebuilding Indexes While logshipping

We implemented logshipping on one of our database and the log is shipped via
wan to different destination.it works great but on weekends we do rebuild
indexes for that databases which generates huge log and it takes forever to
copy that log at least two days.is there a work around for it.
Thanks,
We had the same problem, so we stopped rebuilding index's until a solution
is found. It was more important to have disaster recovery than index's that
are not defragged.
Sorry cant help more.
regards
steve
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:DAF0B62E-AC27-4766-8366-371101325AD4@.microsoft.com...
> We implemented logshipping on one of our database and the log is shipped
> via
> wan to different destination.it works great but on weekends we do rebuild
> indexes for that databases which generates huge log and it takes forever
> to
> copy that log at least two days.is there a work around for it.
> Thanks,
|||place the DB in bulk logged mode during index maintenance. this will reduce
logging for index changs.
Greg Jackson
PDX, Oregon
|||Actually that does not help with log shipping. While it will reduce the
amount of data sent to the transaction log the backup itself will include
ALL the changes and will be just as large.
Andrew J. Kelly SQL MVP
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
> place the DB in bulk logged mode during index maintenance. this will
> reduce logging for index changs.
>
> Greg Jackson
> PDX, Oregon
>
|||I agree with Andrew because i tested it and it didn't make a difference.
"Andrew J. Kelly" wrote:

> Actually that does not help with log shipping. While it will reduce the
> amount of data sent to the transaction log the backup itself will include
> ALL the changes and will be just as large.
> --
> Andrew J. Kelly SQL MVP
>
> "pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
> news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
>
>
|||One thing you should look at is only rebuild indexes that actually need it.
This KB should be helpful and there is a sample script in BooksOnLine under
DBCC SHOWCONTIG that will only reindex the indexes that are fragmented
beyond a certain point. This should cut down the amount that is being
logged dramatically.
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:FF010CDA-3598-4607-8DE2-0BECECE5593D@.microsoft.com...[vbcol=seagreen]
>I agree with Andrew because i tested it and it didn't make a difference.
> "Andrew J. Kelly" wrote:
|||hmm...that's too bad.
How about:
1. disable Log Shipping
2. Perform Index Maintenance
3. ReSeed your Standby DB
4. Start logshipping back up
This is a pain, but MUCH better than NOT doing index maintenance...
GAJ