Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Conflicts and missing store procedure Expand / Collapse
Author
Message
Posted Thursday, June 3, 2010 10:53 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 13, 2014 12:45 AM
Points: 7, Visits: 52
Hi All,

I have a conflict issue in my merge replication.

The replication will always run successfully, but all data (new records created on device) failed to
be inserted each time I synchronized to the server.

Below is the error description that I found in the Conflict Viewer:
The row was inserted at 'weirdl - 619054192' but could not be inserted at 'server1.Database3'. Could not find stored procedure 'sp_ins_2A65010E52CC4D519A1E37A31357492D'.


My questions are about the missing store procedure in the error description:
1) From the description above, am I right to assume that the conflict is not caused by any PK/foreign key violation at all?
2) If it is because of the missing store procedure, why was the replication successful? Why was no error message shown? What caused the store procedure to disappear?

This problem happens to all users and the conflicts can be found on all
replicated tables .

A few mons ago (before conflict issue occured), I changed the
@publication_compatibility_level from 80RTM to 90RTM
to enable download only for one of the table.
Could this be one of the cause of the problem?

How do I fix this?

Thanks
Post #932575
Posted Thursday, August 22, 2013 5:03 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, September 9, 2014 3:49 AM
Points: 411, Visits: 1,403
You forgot to mention what type of replication you are running; snapshot, transactional or merge.

There are some tables in each replicated database (their names differ per replication type), generated during the replication initialisation, that describe the articles and supporting procedures and triggers. You can go and read those to determine whether or not your situation is salvagable. However, any changes you make in this situation can be pretty risky (in terms of possible data loss).

You can often fix these problems (information to do so IS provided online by MS and other parties if you search for it), by for example re-generating the missing procedures. Often however you'll see that many more problems arise afterwards. For example due to data being out of sync between the databases. If you're not very sure that you know what to do, I therefore recommend to not try it all and instead simply create a fresh copy of the database(s), setup a new replication and then transfer the existing data from your current database into one of the newly created databases.




Posting Data Etiquette - Jeff Moden
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Post #1487177
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse