| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | monikerRange | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
MSSQL_ENG021286 |
MSSQL_ENG021286 |
MashaMSFT |
mathoma |
09/25/2024 |
sql |
replication |
reference |
|
|
=azuresqldb-mi-current||>=sql-server-2016 |
[!INCLUDE SQL Server SQL MI]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 21286 |
| Event Source | MSSQLSERVER |
| Component | [!INCLUDEssDEnoversion] |
| Symbolic Name | |
| Message Text | Conflict table '%s' does not exist. |
This error is raised if the conflict table for an article listed in sysmergearticles (Transact-SQL) does not actually exist. The error can occur when you attempt to add a column to or drop a column from a table published for merge replication.
Execute DBCC CHECKDB (Transact-SQL) on the database with the missing conflict table to verify there are no data consistency issues.
If the conflict table is missing on a Subscriber, drop the subscription and recreate it. If the conflict table is missing on a Publisher, drop all subscriptions, drop the publication, and then recreate the publication and all subscriptions. For more information, see Publish Data and Database Objects and Subscribe to Publications.