Hi,
I'm running a merge publication on a SQL Server 2000 database with
several anonymous subscribers. I want to change the subscription
expiry from 14 to 28 days. Aside from larger logging tables, are
there any important consequences to doing this? In particular, do I
need to reinitialise the subscriptions before the change takes effect?
Many thanks
Alex
There will be slower syncs. Yes you need to reinitialize.
Hilary Cotter
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
<WombatDeath@.gmail.com> wrote in message
news:1173701986.327352.14330@.h3g2000cwc.googlegrou ps.com...
> Hi,
> I'm running a merge publication on a SQL Server 2000 database with
> several anonymous subscribers. I want to change the subscription
> expiry from 14 to 28 days. Aside from larger logging tables, are
> there any important consequences to doing this? In particular, do I
> need to reinitialise the subscriptions before the change takes effect?
> Many thanks
> Alex
>
|||Thanks Hilary. If I don't reinitialize the existing subscriptions
will they break, or will they just keep the old 14-day expiration time
until I get around to reinitializing them for other reasons?
Thanks
Alex
Tuesday, March 27, 2012
Consequences of changing subscription expiry date SQL Server 2000
Labels:
changing,
consequences,
database,
date,
expiry,
merge,
microsoft,
mysql,
oracle,
publication,
running,
server,
sql,
subscribers,
subscription,
subscriptionexpiry,
withseveral
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment