A subscription has expired and has been dropped

I have two SQL 2000 Servers with Merge Replication. I had a problem on my
link for a month and the "Expired subscription clean up" job dropped the
subscription ! and now I don't know how to replicate the generated data at
the subscriptor.
I appreciate any help.
You will need to re-apply a snapshot to the subscriber...
"gus barraza" wrote:

> I have two SQL 2000 Servers with Merge Replication. I had a problem on my
> link for a month and the "Expired subscription clean up" job dropped the
> subscription ! and now I don't know how to replicate the generated data at
> the subscriptor.
> I appreciate any help.
>
|||Jim the subscription type is PUSH
re-apply a snapshot means that i should PUSH a new subscription again ?
Will I lost the data generated at the subscriber ?
"Jim Breffni" wrote:
[vbcol=seagreen]
> You will need to re-apply a snapshot to the subscriber...
>
> "gus barraza" wrote:
|||Interesting problem.
I don't know of any method of automatically re-syncing after the
subscription has been dropped other than to apply a new snapshot.
Once the subscription has been dropped SQL has no way of keeping track of
changes that need to be applied to the subscriber.
Sounds like you will need a manual process to bring the publisher up to date
with subscriber changes before creating a new snapshot. Not a pleasent
thought...
Redgate do a sql DATA compare tool that will generate sql scripts for you
that will update your tables.
Jim.
"gusbarraza" wrote:
[vbcol=seagreen]
> Jim the subscription type is PUSH
> re-apply a snapshot means that i should PUSH a new subscription again ?
> Will I lost the data generated at the subscriber ?
> "Jim Breffni" wrote:
|||Thank you Jim,
I have my own application to this cases, but I had been confirm my suspects,
that the only way to recover data on the subscriber is through this slow
process.
I should start to make this process...
"Jim Breffni" wrote:
[vbcol=seagreen]
> Interesting problem.
> I don't know of any method of automatically re-syncing after the
> subscription has been dropped other than to apply a new snapshot.
> Once the subscription has been dropped SQL has no way of keeping track of
> changes that need to be applied to the subscriber.
> Sounds like you will need a manual process to bring the publisher up to date
> with subscriber changes before creating a new snapshot. Not a pleasent
> thought...
> Redgate do a sql DATA compare tool that will generate sql scripts for you
> that will update your tables.
>
> Jim.
>
> "gusbarraza" wrote:

A MergeJoin using two fields doesnt work !

Hi,

I have an issue. When I am performing a Merge Join using two fields of type
DT_WSTR on both sides of the Join, the Dataviewer after the Join only shows the left side 2 key
fields having values populated but both fields from the right hand side as being NULL. The Dataviewers I put in before the join show both sides of the join fields being populated ( 2 sides x 2 fields ). If I remove one of the fields from the join it shows both fields from the left side and the right side of the join being populated . I am trying to knock out duplicate values from the insert using 'genuine' Nulls from the right hand side so I need both parts of the 'Key'. I have checked the adnvanced tab that ignores Case etc but has had no effect.

I am using the technique from here : http://www.sqlis.com/311.aspx

Is this an SSIS bug ? It is driving me up the wall.

Help would be much appreciated please.

Thanks
Jon

SORTED !!

Sorry for this wasted post but this may be usefull for someone else in the future.

I changed the package to perform a lookup instead of a merge join and that failed as well. When I looked at the DB one of the two fields I was looking up to was defined as an NCHAR(15) and so always had whitespace at the end. I changed the datatype to be an NVARCHAR(15), reloaded the contents of the field and Voila, all was well.

Thanks anyway.

Jon

A Little Basic Help needed (SQLServer 2005) Merge Replication

Hi all,

We are using SQL Server 2005, on Windows server 2003 R2.

We Have Two Database Servers say DBServer1 and DBServer2, Now I wants to do Replication between these to servers, such that

1. The Changes at DBServer1 should be reflected at DBServer2
2. The Changes at DBServer2 should be reflected at DBServer1
3. Changes includes Data changes and Schema Changes
4. After every Synchronization Both Databases should be Identical

I tried doing so, what i did was
I cofigured Distribution at DBServer1, also Publisher and Publication at DBServer1
and Made a Subscription at DBServer2.

What I successfully done is
If Publisher means DBServer1 do some changes then it gets updated at DBServer2.
But New Rows added at DBServer2 doesn't gets added at DBServer1

Thanks in Advance,
Vishalgiri Goswami
Kalptaru Infosoft Pvt. Ltd.Did you start the merge agent job? The merge agent does the synchronization.|||Yes Sir, Merge Agent is Running, I have Sheduled it to Run at 5 min Interval, I am viewing it's status from View Synchronization Option.

Even My Snapshot Agent is running too.|||Did you define a subset filter clause? And did your subscriber even download the snapshot? The snapshot agent doesn't need to run every 5 minutes.|||DId your subscriber download the schema from the snapshot? Does your publication have filtering, if yes, what does the subset filtering clause look like?