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 : Deleted Records Keep Reapearing

Im currently having problems with merge replication.

Example:

When a customer record is deleted from tbl_customers its removed from the table, then its reappears about 30s - 1min later?

Im presuming the other server is restoring the record though replication.

Any Insight in to this would be most appreciated.

DanielI've found the error but still not to sure why its occuring?

Heres the errors
------

"The row was deleted at 'ENTERPRISE.PMSPS' but could not be deleted at 'VOYAGER.PMSPS'. Invalid object name 'tbl_contacts'."

[Conflict Winner]
The error described above occurred when trying to delete this row. If you ignore this conflict, you should resolve it through other means. Consider logging the details of this conflict, then sending the log entry to your system administrator. The value of the unique ID in column 'rowguid' is '{D2604393-EBB4-4CF7-97BC-562C28B6BD1B}'.

[Conflict Loser]
This row has been deleted. If you choose to ignore the conflict, Microsoft SQL Server will try to reinsert the deleted row, using data from the other server.

I have the option to Keep winning change which will just put the record back in or I can Resubmit the DELETE which just comes back with the same error.

:(

Replication

When replication was taking place and when we tried to enter records in ERP Package i.e Navision we faced the following error.

231,”21s01”,[Microsoft][ODBC SQL Server Driver][SQL Server]Insert Error: Column name or number of supplied values does not match table definition.

Can anybody help me in resolving this.Please mail to me at

ranjit246@.yahoo.co.in

Merge replication requires every table article to contain a uniqueidentifier column with rowguid property set. If one doesn't exist, we add it. This column does have a DEFAULT constraint defined, so if you specify column list when doing your insert, this rowguid column will be transparent to your application.

It's good practice to specify a column list for all insert statements, I'm guessing your application doesn't do this, which is why your app is failing.

|||

Where do i make this change. I am using the DataSouce in VB DataViewGrid.

Please help

Replication

When replication was taking place and when we tried to enter records in ERP Package i.e Navision we faced the following error.

231,”21s01”,[Microsoft][ODBC SQL Server Driver][SQL Server]Insert Error: Column name or number of supplied values does not match table definition.

Can anybody help me in resolving this.Please mail to me at

ranjit246@.yahoo.co.in

Merge replication requires every table article to contain a uniqueidentifier column with rowguid property set. If one doesn't exist, we add it. This column does have a DEFAULT constraint defined, so if you specify column list when doing your insert, this rowguid column will be transparent to your application.

It's good practice to specify a column list for all insert statements, I'm guessing your application doesn't do this, which is why your app is failing.

|||

Where do i make this change. I am using the DataSouce in VB DataViewGrid.

Please help

replicating the resultset of a view

hello all,

I created a view and I want the result set(records) of the view to be replicated to another server. i've tried replicating the view by checking the view in the replication wizard but it seems that only the definition of the view is being replicated. Is there a way that i can fullfill the desired result through replication. That to store the result of the view to a new table in the replication destination. I'm using snapshot replication

thanks in advance

joey

Hi Joey,

I saw that Paul Ibison has already suggested that you publish your view as an indexed view to table article (or the slightly misnamed 'indexed view logbased' type article) on the microsoft.public.sqlserver.replication newsgroup. This is probably the easiest solution to your problem although creating a unique index on your view may impair update performance at your publisher. If your view is defined to return a subset of columns for one of your tables, you may want to publish the underlying table with horizontal\vertical filters that match your view definition. We will also consider to simply allow the scenario that you described in a future release.

Thanks for your feedback.

-Raymond