replication conflicts for 2 tables

Hi,
we are using merge replication between remote sites and
our central office. couple months ago we had a situation
where we had to insert some records and update other
records with these inserted records and then delete the
inserted records. Then we reinserted these records again
without replicating the deletes to our remote sites.
by doing this we had lots of conflicts.
I mannually deleted replicated and reinserted the records
again.
all other sites are fine but 2 of our sites, which were
disconnected during the delete replication did not get the
deleted records and they still shows conflicts every day
when they replicate. even though these records are not
being edited at all. For some reason they get marked for
replication and shows up in conflicts.
we don't care if those changes doesn't get replicated to
the remote sites becos they don't need those changes. how
do I stop them to show up in conflicts.
thanks
Kiran
did you resolve these conflicts using the conflict viewer? This is the
preferred way of solving this problem?
"Kiran" <anonymous@.discussions.microsoft.com> wrote in message
news:16bc201c41752$0defc130$a101280a@.phx.gbl...
> Hi,
> we are using merge replication between remote sites and
> our central office. couple months ago we had a situation
> where we had to insert some records and update other
> records with these inserted records and then delete the
> inserted records. Then we reinserted these records again
> without replicating the deletes to our remote sites.
> by doing this we had lots of conflicts.
> I mannually deleted replicated and reinserted the records
> again.
> all other sites are fine but 2 of our sites, which were
> disconnected during the delete replication did not get the
> deleted records and they still shows conflicts every day
> when they replicate. even though these records are not
> being edited at all. For some reason they get marked for
> replication and shows up in conflicts.
> we don't care if those changes doesn't get replicated to
> the remote sites becos they don't need those changes. how
> do I stop them to show up in conflicts.
> thanks
> Kiran
sql

Replication Clean Up of Failed Server

On my distribution server, I have a failed replication (the big red X) for a
server that had hardware failure a couple of weeks ago. We were able to
bring this client up on a separate server and have re-replicated them. Now
I need to get rid of the failed replication however when I try to simply
delete it, it obviously cannot connect to the failed server since it doesn't
exist and therefore will not delete the information from the DISTRIBUTOR.
I would like to avoid manual system table clean up unless someone has the
method that will completely remove this information.
Is there a way to do this correctly?
Thanks,
Adam P. Cassidy
Did you follow these instructions?
http://support.microsoft.com/kb/324401
Also on your distributor you may have to issue a call to
sp_dropdistpublisher
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
"Adam Patrick Cassidy" <apcassidy@.aol.com> wrote in message
news:OnM$cTvaHHA.2436@.TK2MSFTNGP06.phx.gbl...
> On my distribution server, I have a failed replication (the big red X) for
> a
> server that had hardware failure a couple of weeks ago. We were able to
> bring this client up on a separate server and have re-replicated them.
> Now
> I need to get rid of the failed replication however when I try to simply
> delete it, it obviously cannot connect to the failed server since it
> doesn't
> exist and therefore will not delete the information from the DISTRIBUTOR.
> I would like to avoid manual system table clean up unless someone has the
> method that will completely remove this information.
> Is there a way to do this correctly?
> Thanks,
>
> Adam P. Cassidy
>

Replicating Lookup Data

Hello, I have a couple of tables containing lookup data I need to replicate
into a database on a different server.
Originally I was just copying the data acros via DTS but now the target
tables are referenced by a foreign keys on a table this no longer works as I
cannot clear the tables out before loading.
I'm contemplating using DTS to load the lookup's in to tempdb on the target
server then use a stored proc to either insert or update a row in the lookups
depending n if they exist or not. Can I simplify this solution using a method
of replication. The data only need's to be update nightly!
Thanks
Adam
I'd use transactional replication which'll jusst take noghtly changes. The
FKs aren't really needed on the subscriber as the data is lookup only and
the FKs must have been checked on the publisher. Even so, FK not for
replication would perhaps be ideal (this is the default now).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Sorry, I didn't make it clear. The table I'm replicating is a list of
locations which need's to be used in another different database. The main
data table in the target database has the foreign key which links to the
location table. There is no foreign key on the source table! If I use
transactional replication, can I ignore deletes?
Thanks
Adam
"Paul Ibison" wrote:

> I'd use transactional replication which'll jusst take noghtly changes. The
> FKs aren't really needed on the subscriber as the data is lookup only and
> the FKs must have been checked on the publisher. Even so, FK not for
> replication would perhaps be ideal (this is the default now).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
|||Yes - you can enter NONE for the replicayed command in the article
properties (@.del_cmd).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com