Are you sure you really need to reindex? Depending on your DML patters
sometimes you don't need to and residual defragmentation is the same as
before.
When you reinidex your tlog blows up and your log reader agent has to work
harder than before. You might want to bump its querytimeout value.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com [quoted text, click to view] "Methodology" <Methodology@discussions.microsoft.com> wrote in message
news:031618ED-A14A-4DB3-A8C1-6504220B952C@microsoft.com...
> Hi
>
> I need to setup replication from one DB to another. Primary DB is 150GB.
> Every Saturday a full re-index is done on the DB which is obviously going
> to
> create a HUGE transaction. As my replica server is geographically remote -
> ie
> contactable over a WAN im thinking that there arent going to be enough
> hours
> in the weekend to get this data over (i will only replicate during 12
> hours
> at night).
>
> I havent set up a test lab for this yet though Im going to - I just
> wondered
> if anybody had anything to say on the subject? Am I right that this
> problem
> will totally stuff up my replication? Will a huge Transaction be created?
> If
> I'm doomed doing things this way, what other method could I use?
>
> Thanks in Advance
>
> Alastair Jones
> Methodology Group.