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 merge distribution change my table definitions at publisher

I have merge replication between sql 2005 SP1, and when I disable distribution from my publisher, my tables with identity columns change the property "Not for replication" to "NO", does somebody knows if this is a known problem ?

Other information : the compatibilty level for database is 2000.

Do you see a problem with that?

Typically when replication is involved, Not For Replication is needed because when the identity value is tried to insert on the other node, this constraint needs to be skipped. Now with no replication on the machine, it would not matter if this property is ON or OFF.

Disable constraint creation for subscriber

Hello,

It seems we have a table that is on merge replication the table by default doesn't have a PK on it. This table only has about 50 rows of data, somewhere during the initialization process it's trying to create a PK by default on the client end. My assumption is during the creation of the snapshot a script is being generated that we do not want. How can we prevent them from happening as it's creating a PK violation.

The schema script 'if object_id(N'[dbo].[checklistimported]') is not null exec('ALTER TABLE [dbo].[checklistimported] ADD CONSTRAINT
PK_listimported PRIMARY KEY CLUSTERED
(
projectid,
chklstid,
unit,
lot
) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

')' could not be propagated to the subscriber due to an error in creating index. A possible cause of this error is one or more join filters has the join_unique_key property se

server SQL2k5 SP1

client SQL Express

Actually the PK should have existed at the publisher side. If it does not exist at the publisher side, it will not be created at the subscriber side.

Are the two servers (publisher and subscriber) with the same case sensitivity? I am suspecting that's the problem.