>-----Original Message-----
>you have to do several things to get this to work. The
retention period in
>your publication properties should match
>
>1) the transaction retention period for your distribution
database. In EM
>click Tools, point to replication, click configure
Publishers, Susbcribers,
>and Distributors. On the Distributor tab, click
properties and make sure
>that the transaction retention has a minimun of 0 hours,
and a maximunn (the
>But Not More than option) that matches what you have for
the transaction
>retention period of your Publication properties. By
default 336 hours.
>
>2) Make sure your history retention period also matches
whatever you pick
>for your subscription expiration period. The default for
the history
>retention period is also 48 hours, you should bump it up
to 336.
>
>The problem is that if your subscribers go offline for
long periods of time
>your distribution database will grow very large
(depending on the number of
>transactions in it). Specifically your
msrepl_transactions and especially
>msrepl_commands tables get very large. When these tables
get large
>replication performance degrades significantly and your
overall database
>performance could be impacted as well.
>
>So you need to be highly proactive in making sure the
links that connect
>your publisher and subscriber are always up. I monitor my
distribution
>history table to see if a particular subscriber has not
talked to the
>publisher over the past day, and if not I fix or escalate
the problem.
>
>On some applications you will need to ensure that your
latency is far less
>than a day, for instance on one project I worked on we
had a latency of 10
>minutes. So you will sometimes need to be highly
proactive, and will need
>some form of network monitoring software (like NetIQ,
BMC, etc) to alert you
>of failures like this.
>
>
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>
>"Javi" <javisimsa@hotmail.com> wrote in message
>news:595f01c4748e$095a2fe0$a301280a@phx.gbl...
>> I have an irritating problem with an extraction
>> subscription that expires unexpectedly before it should.
>> On the publication I have set the expire time at 336
hours
>> but the subscription expires much before. It's an
>> SQLServer bug or I'm doing something wrong? The real
>> problem is have to reinit the subscription every time
that
>> it expires. I wouldn't like to have to do it again.
>>
>> Thank you.
>
>
>.