Disappearing conflicts and snapshot

Hi ng,
we have serious problem,
we administrating one merge replication between Sql 2000 Serwers,
we had about 1000 conflicts in ConflictViewer,
we wanted to resolve this conflicts in monday, but during the weekend new
snapshot was generated and our all conflicts disappeared.
now we have no data from subscriber refered to this conflicts and we don't
know what to do?
we tried to update all records at the subscriber, but this didn't help, all
records was replicated except this 1000 conflicted,
thanks for any help
pozdrawiam
Kuba Guszkiewicz
k.gluszkiewicz@.citysoftware.com.pl
tel. 509-650-351
(22) 869-51-76
(22) 869-51-77
fax (22) 869-51-78
restore the publisher backup (from a day before the snapshot was generated)
on a separate server. You will find them there.
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
"Kuba Guszkiewicz" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
news:%23YhmBdtsFHA.2592@.TK2MSFTNGP09.phx.gbl...
> Hi ng,
> we have serious problem,
> we administrating one merge replication between Sql 2000 Serwers,
> we had about 1000 conflicts in ConflictViewer,
> we wanted to resolve this conflicts in monday, but during the weekend new
> snapshot was generated and our all conflicts disappeared.
> now we have no data from subscriber refered to this conflicts and we don't
> know what to do?
> we tried to update all records at the subscriber, but this didn't help,
all
> records was replicated except this 1000 conflicted,
> thanks for any help
> --
> pozdrawiam
> Kuba Guszkiewicz
> k.gluszkiewicz@.citysoftware.com.pl
> tel. 509-650-351
> (22) 869-51-76
> (22) 869-51-77
> fax (22) 869-51-78
>
|||Hilary,
many thanks for your advice,
indeed, we have that backup, but i'm not sure how to restore this on another
database,
could you tell me some more details?
tia
kg
|||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
"Kuba Guszkiewicz" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
news:%23K3J21usFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hilary,
> many thanks for your advice,
> indeed, we have that backup, but i'm not sure how to restore this on
another
> database,
> could you tell me some more details?
> tia
> kg
>
|||Create a new database, and restore the backup into this database. Use the
keep_replication switch.
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
"Kuba Guszkiewicz" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
news:%23K3J21usFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hilary,
> many thanks for your advice,
> indeed, we have that backup, but i'm not sure how to restore this on
another
> database,
> could you tell me some more details?
> tia
> kg
>

Disabling a publication replication schedule programatically

Is there a way that I can programatically disable a publication from
replicating if publication conflicts exists? My intent is to check is there
is publications conflicts for the pub and prevent it from replicating on its
next scheduled replication if previous conflicts exist.
You should really be trying to resolve the sources of conflict so that they
do not re-occur rather than trying to do what you propose.
With replication you want conflicts to be rare and/or trivial.
"Pete Ocasio" wrote:

> Is there a way that I can programatically disable a publication from
> replicating if publication conflicts exists? My intent is to check is there
> is publications conflicts for the pub and prevent it from replicating on its
> next scheduled replication if previous conflicts exist.
>
>
|||Thanks for your answer. I have infact tried to fix the problem. The
biggest problem is the weakest link in the chain: users. They refuse to
follow instructions even when the instructions are clear and even, written
for them. Even after they experienced a problem more than once, they
insist in repeating it. Any other ideas?
"Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
news:4CD4DEF5-6172-49A7-8265-3EA4E875CF6B@.microsoft.com...
> You should really be trying to resolve the sources of conflict so that
they[vbcol=seagreen]
> do not re-occur rather than trying to do what you propose.
> With replication you want conflicts to be rare and/or trivial.
>
> "Pete Ocasio" wrote:
there[vbcol=seagreen]
its[vbcol=seagreen]
|||See my post on your other thread - I suspect the two problems are related.