| title | sp_helpmergeconflictrows (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql-server-2016 | ||
| ms.reviewer | |||
| ms.suite | |||
| ms.technology |
|
||
| ms.tgt_pltfrm | |||
| ms.topic | language-reference | ||
| applies_to |
|
||
| f1_keywords |
|
||
| helpviewer_keywords |
|
||
| ms.assetid | 131395a5-cb18-4795-a7ae-fa09d8ff347f | ||
| caps.latest.revision | 21 | ||
| author | BYHAM | ||
| ms.author | rickbyh | ||
| manager | jhubbard |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx_md]
Returns the rows in the specified conflict table. This stored procedure is run on the computer where the conflict table is stored.
Transact-SQL Syntax Conventions
sp_helpmergeconflictrows [ [ @publication = ] 'publication' ]
, [ @conflict_table = ] 'conflict_table'
[ , [ @publisher = ] 'publisher' ]
[ , [ @publisher_db = ] 'publsher_db' ]
[ , [ @logical_record_conflicts = ] logical_record_conflicts ]
[ @publication=] 'publication'
Is the name of the publication. publication is sysname, with a default of %. If the publication is specified, all conflicts qualified by the publication are returned. For example, if the MSmerge_conflict_Customers table has conflict rows for the WA and the CA publications, passing in a publication name CA retrieves conflicts that pertain to the CA publication.
[ @conflict_table=] 'conflict_table'
Is the name of the conflict table. conflict_table is sysname, with no default. In [!INCLUDEmsCoName] [!INCLUDEssVersion2005] and later versions, conflict tables are named using the format names with MSmerge_conflict_publication_article, with one table for each published article.
[ @publisher=] 'publisher'
Is the name of the Publisher. publisher is sysname, with a default of NULL.
[ @publisher_db=] 'publisher_db'
Is the name of the publisher database.publisher_db is sysname, with a default of NULL.
[ @logical_record_conflicts= ] logical_record_conflicts
Indicates whether the result set contains information about logical record conflicts. logical_record_conflicts is int, with a default value of 0. 1 means that logical record conflict information is returned.
sp_helpmergeconflictrows returns a result set consisting of the base table structure and these additional columns.
| Column name | Data type | Description |
|---|---|---|
| origin_datasource | varchar(255) | Origin of the conflict. |
| conflict_type | int | Code indicating the type of conflict: 1 = Update Conflict: The conflict is detected at the row level. 2 = Column Update Conflict: The conflict detected at the column level. 3 = Update Delete Wins Conflict: The delete wins the conflict. 4 = Update Wins Delete Conflict: The deleted rowguid that loses the conflict is recorded in this table. 5 = Upload Insert Failed: The insert from Subscriber could not be applied at the Publisher. 6 = Download Insert Failed: The insert from Publisher could not be applied at the Subscriber. 7 = Upload Delete Failed: The delete at Subscriber could not be uploaded to the Publisher. 8 = Download Delete Failed: The delete at Publisher could not be downloaded to the Subscriber. 9 = Upload Update Failed: The update at Subscriber could not be applied at the Publisher. 10 = Download Update Failed: The update at Publisher could not be applied to the Subscriber. 12 = Logical Record Update Wins Delete: The deleted logical record that loses the conflict is recorded in this table. 13 = Logical Record Conflict Insert Update: Insert to a logical record conflicts with an update. 14 = Logical Record Delete Wins Update Conflict: The updated logical record that loses the conflict is recorded in this table. |
| reason_code | int | Error code that can be context-sensitive. |
| reason_text | varchar(720) | Error description that can be context-sensitive. |
| pubid | uniqueidentifier | Publication identifier. |
| MSrepl_create_time | datetime | Time the conflict information was added. |
0 (success) or 1 (failure)
sp_helpmergeconflictrows is used in merge replication.
Only members of the sysadmin fixed server role, the db_owner fixed database role, and the replmonitor role in the distribution database can execute sp_helpmergeconflictrows.
View Conflict Information for Merge Publications (Replication Transact-SQL Programming)
Replication Stored Procedures (Transact-SQL)