How To Fix General MSSQL Error 2627
Table of Contents
Updated
Sometimes your computer may generate an error code stating the generic mssql error 2627. There can be many reasons for this problem to occur. This issue occurs because the cached sequence type is reset incorrectly each time the database is backed up. This makes the la value of some cached sequences larger than the la value that is still on disk. In this situation, error 2627 is generated.
In This Article
Applies to: SQL Server (all supported
Managed versions) Azure SQL Instance
Message Details
| Attribute | value | |
|---|---|---|
| Product Server | ||
| Event name | SQL identifier | 2627 |
| Event Source | MSSQLSERVER | |
| Component | SQL Server Database Engine | |
| Symbolic name | Not applicable | |
| Message body | Violation of %ls constraint for ‘%.*ls’. Cannot insert duplicate key into object ‘%.*ls’. |
Explanation
This is a general errora, which is easy to call whether the database is up for new replication or not. In replicated lists, the error is usually caused by incorrect distribution of primary keys in the topology. In distributed parts of your environment, it’s important to make sure that the same value isn’t always inserted into an important primary column or another unique row across multiple nodes. Possible reasons:
Inserts and advances in a series occurring at more than one node. Handling updatable transactions and merge subscriptions provide conflict detection and resolution, but it’s always best if data is inserted or updated on the same node. Peer-to-peer non-transactions detect and do not resolve conflicts; Inserts as well as updates should be separated.
A string is attached to the subscriber and should be read-only. Subscribers to snapshot publications should be treated as read-only, as are subscribers to transactional publications, except when updatables are actually used.e or subscription peer-to-peer transactional replication.
The one with the ID beam table is used, but the smile is handled incorrectly. Required
User Action
The process depends on why this error was returned:
Inserts and updates that return to the same row do not only occur on the first node.
Whatever specific type of replication we’re using, it’s a good idea to call in experts to insert and update partitions if possible, as this reduces the number of operations required to detect and resolve conflicts. Peer-to-peer transactional replication requires separation of attachments and updates. For more information, see Peer-to-Peer Transactional Replication.
A subscriber had a row inserted that should be read-only.
If you’re using merge replication, transactional with replication-updated subscriptions, perhaps peer-to-peer replication, transactional probably doesn’t include updated subscriber rows.
A .table .with.a .i .. D . The column is being used because the particular column is not being handled properly.
For combined replication and transactional replication charges, updatable identity columns should be automatically replaced by replication. For peer-to-peer copying of articles, directories must be managed in many transactional ways. For details, see Replicating View Columns
Identity.
See See Also
Error link and event (replication)
Merge replication
Peer-to-Peer Transaction Replication
Scalable Transactional Replication Subscriptions