From: OceanDeep via SQLMonster.com on
We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. The publisher and distributor are on the same server.

Out of nowhere, I received the following message.

The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.

The subscription setting in the publisher is 'never expire'. The retention
settings in the distributor are as follows:

Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: store replication performance History at least 48 hours.

Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
for over 2 years as the default is set to 'never expire' I think. So what
happened to my subscription? why all of a sudden, this error comes up. What
is the solution for it?


Any help on this is very much appreciated.

od

--
Message posted via http://www.sqlmonster.com

From: Ben Thul on
How do you monitor your replication? Do you know that your subscriber
wasn't more that 72 hours behind the publisher? If it got outside of
that threshold, that would make the subscription expire, regardless of
settings. Other than that, I can't think of another reason why that
would happen.
--
Ben
On Aug 12, 4:07 pm, "OceanDeep via SQLMonster.com" <u46587(a)uwe> wrote:
> We are using SQL 2008 std with push transactional publishation to a SQL 2005
> subscriber.  The publisher and distributor are on the same server.
>
> Out of nowhere, I received the following message.
>
> The subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated.
>
> The subscription setting in the publisher is 'never expire'.   The retention
> settings in the distributor are as follows:
>
> Transaction retention: At least 0 hours and but not more than 72 hours.
> History retention:  store replication performance History at least 48 hours.
>
> Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
> for over 2 years as the default is set to 'never expire' I think.  So what
> happened to my subscription?  why all of a sudden, this error comes up.  What
> is the solution for it?
>
> Any help on this is very much appreciated.
>
> od
>
> --
> Message posted viahttp://www.sqlmonster.com