Log shipping and index rebuilds

Hi everyone.
My company is embarking on a DRP project where we will move our production s
ervers to a less geographically insecure area. We'll need to perform log shi
pping back to our DRP site here in Vancouver Canada.
I just learned today that SQL Server logs index rebuilds and that we perform
rebuilds regularly so I have a few questions if anyone can help:
Can we stop index builds from being logged?
If we cannot stop index logging, are there any different practices we can fo
llow to do index maintenance that will not require logging (e.g. defrag)
Are there best practices around log shipping for MS-SQL that will maximize o
ur use of bandwidth?
Does anyone have any experience of this?
If we were to ship index rebuilds, we'll be shipping gigabytes of unnecessar
y data, but apparently SQL Server will not let this be switched off?
Thanks.
David.David,
I have implemented LogShipping at my site and understand your questions. For
the most indepth information on LogShipping and High Availability, check ou
t this book. You will find that it answers all of your questions and way mor
e.
SQL Server 2000 High Availability.
It's from Microsoft Press and it discusses everything you may want to know.
This may be not the answer you were expecting, but I am sure once you pick u
p the book that you will have answers to questions you didn't know you had.
Lisa
"davidbailie" wrote:

> Hi everyone.
> My company is embarking on a DRP project where we will move our production
servers to a less geographically insecure area. We'll need to perform log s
hipping back to our DRP site here in Vancouver Canada.
> I just learned today that SQL Server logs index rebuilds and that we perfo
rm rebuilds regularly so I have a few questions if anyone can help:
> Can we stop index builds from being logged?
> If we cannot stop index logging, are there any different practices we can
follow to do index maintenance that will not require logging (e.g. defrag)
> Are there best practices around log shipping for MS-SQL that will maximize
our use of bandwidth?
> Does anyone have any experience of this?
> If we were to ship index rebuilds, we'll be shipping gigabytes of unnecess
ary data, but apparently SQL Server will not let this be switched off?
> Thanks.
> David.
>|||Lisa, thanks very much for your reply. I happen to have that book (one of th
e many I haven't even opened yet). But I'll take a look through it.
Thanks again,
David.
--
David Bailie
Ernex
Vancouver, BC.
Canada
"Ora/SQL DBA" wrote:
[vbcol=seagreen]
> David,
> I have implemented LogShipping at my site and understand your questions. F
or the most indepth information on LogShipping and High Availability, check
out this book. You will find that it answers all of your questions and way m
ore.
> SQL Server 2000 High Availability.
> It's from Microsoft Press and it discusses everything you may want to know
.
> This may be not the answer you were expecting, but I am sure once you pick
up the book that you will have answers to questions you didn't know you had
.
> Lisa
> "davidbailie" wrote:
>