|
Home > Archive > MS SQL Server Replication > December 2006 > Lost data
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Maverick06 2006-11-29, 7:16 pm |
| HELP!!!!
I have a republisher model type merge replication and a table in the second
level of replication is losing all its data and from there its subscriber
loses its data also........
| |
| Hilary Cotter 2006-11-29, 7:16 pm |
| Check the conflict viewer there to see if it is logged as conflicts.
How did you set republishing up? It should be from upstream to downstream.
Start with your highest level publisher, and publish to downstream
publishers. The data in the downstream publishers will get whacked. Then
when the data is in the downstream publishers publish to the subscribers.
Is this SQL 2000 or SQL 2005. You need to configure them differently for the
version.
--
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
"Maverick06" <u29745@uwe> wrote in message news:6a052e272c643@u
we...
> HELP!!!!
> I have a republisher model type merge replication and a table in the
> second
> level of replication is losing all its data and from there its subscriber
> loses its data also........
>
| |
| Maverick06 2006-11-30, 7:17 pm |
| It's SQL Server 2000,
I have set up my replication in a top down approach. The merge agent
started and got stuck in a loop I presume. There was alot of data to
transfert.... But nothing was happening and I restarted the sql Server
and when it restarted it truncated my whole table... All the was gone
from the republisher.. There's no conflicts... I have testeed the same
scenario with same structure, while it was downloading the data I
stopped the sql Server and when it came back online it picked up where
it left without an itch. It's the second time I loose all my data in 2
different ways...
Hilary Cotter wrote:
> Check the conflict viewer there to see if it is logged as conflicts.
>
> How did you set republishing up? It should be from upstream to downstream.
> Start with your highest level publisher, and publish to downstream
> publishers. The data in the downstream publishers will get whacked. Then
> when the data is in the downstream publishers publish to the subscribers.
>
> Is this SQL 2000 or SQL 2005. You need to configure them differently for the
> version.
> --
> 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
| |
| Hilary Cotter 2006-12-01, 7:15 pm |
| This is by design. When you stopped the initial sync the next time it
restarted it had to truncate the table and repopulate it. Sometimes initial
syncs for large tables can be lengthy.
--
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
"Maverick06" < swift_kick125@hotmai
l.com> wrote in message
news:1164913159.947731.53550@f1g2000cwa.googlegroups.com...
> It's SQL Server 2000,
> I have set up my replication in a top down approach. The merge agent
> started and got stuck in a loop I presume. There was alot of data to
> transfert.... But nothing was happening and I restarted the sql Server
> and when it restarted it truncated my whole table... All the was gone
> from the republisher.. There's no conflicts... I have testeed the same
> scenario with same structure, while it was downloading the data I
> stopped the sql Server and when it came back online it picked up where
> it left without an itch. It's the second time I loose all my data in 2
> different ways...
>
>
> Hilary Cotter wrote:
>
|
|
|
|
|