Pull Merge - Subscription Expired

I have a subscription that has expired. I need to be careful to preserve
the data that resides at my subscriber. I have two weeks worth of data at
the subscriber that needs to be synchronized with the publisher. Any
recommendations on the best approach to get my subscriber back in sync?
Thanks
Tina
re-initialize your merge subscription. When you re-initialize it you will
get a prompt to upload the changes from the subscriber to the publisher.
This will ensure that these changes are not lost.
"Tina Smith" <tb.smith@.earthlink.net> wrote in message
news:OWNyJX9KEHA.1032@.tk2msftngp13.phx.gbl...
> I have a subscription that has expired. I need to be careful to preserve
> the data that resides at my subscriber. I have two weeks worth of data
at
> the subscriber that needs to be synchronized with the publisher. Any
> recommendations on the best approach to get my subscriber back in sync?
> Thanks
> Tina
>
|||Sounds good! I'm hoping the re-init can be done via the
sp_reinitmergesubscription stored procedure because I'm running MSDE at the
subscribers.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%234twWk$KEHA.3492@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> re-initialize your merge subscription. When you re-initialize it you will
> get a prompt to upload the changes from the subscriber to the publisher.
> This will ensure that these changes are not lost.
> "Tina Smith" <tb.smith@.earthlink.net> wrote in message
> news:OWNyJX9KEHA.1032@.tk2msftngp13.phx.gbl...
preserve[vbcol=seagreen]
data
> at
>

Publication has expired

I have setup transaction replication using seperate server for distribution
box.
Server A - Publisher (Win2003, SQL2000 SP818)
Server B - Distributor (Win2003, SQL2000 SP818)
Server C - Subscriber1 (Win2003 and SQL2000 SP818)
Server D - Subscriber2 (Win2003 and SQL2000 SP818)
Server E - Subscriber3 (Win2000, SQL2000 SP818)
Server A has 3 publishers and each publisher has more than 10 articles, one
of them we use it for monitoring replication by update a datetime column from
sql job.
The trans. replication are running fine execpt the subscriber3. This
subsciber always get sthe subscription expires errors, but the monitor
article does get updated. And the wired thing is the replication monitor on
the distribution server shows that the agent is in suspect and no reponse
within 10 min after each snapshot/initation.
I did query the MSDistribution_History and there is only one row which the
date I ran the snspshot. All the retention and history period are default.
Does anyone knows that it is Win2003 to Win2000 issue or something else.
Thanks in advance
This guy expired prematurely because your history retention is less than
your publication retention. Bump this setting up to your publication
retention, and be highly proactive about sensing when this guy has dropped
off the network for more than 1 day.
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
"kc" <kc@.discussions.microsoft.com> wrote in message
news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> I have setup transaction replication using seperate server for
distribution
> box.
> Server A - Publisher (Win2003, SQL2000 SP818)
> Server B - Distributor (Win2003, SQL2000 SP818)
> Server C - Subscriber1 (Win2003 and SQL2000 SP818)
> Server D - Subscriber2 (Win2003 and SQL2000 SP818)
> Server E - Subscriber3 (Win2000, SQL2000 SP818)
> Server A has 3 publishers and each publisher has more than 10 articles,
one
> of them we use it for monitoring replication by update a datetime column
from
> sql job.
> The trans. replication are running fine execpt the subscriber3. This
> subsciber always get sthe subscription expires errors, but the monitor
> article does get updated. And the wired thing is the replication monitor
on
> the distribution server shows that the agent is in suspect and no reponse
> within 10 min after each snapshot/initation.
> I did query the MSDistribution_History and there is only one row which the
> date I ran the snspshot. All the retention and history period are
default.
> Does anyone knows that it is Win2003 to Win2000 issue or something else.
> Thanks in advance
|||In my case, the monitor article in the subscriber had same time as the
publisher when it was mark for expiration. Therefore it is not a network
issue.
By default, the hsitory rentention is 48 hrs and transaction rentention is
72 hrs, so I don't understand what do you mean that I need to bump the
setting up?
Thanks
KC
"Hilary Cotter" wrote:

> This guy expired prematurely because your history retention is less than
> your publication retention. Bump this setting up to your publication
> retention, and be highly proactive about sensing when this guy has dropped
> off the network for more than 1 day.
> --
> 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
> "kc" <kc@.discussions.microsoft.com> wrote in message
> news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> distribution
> one
> from
> on
> default.
>
>