Operational Defect Database
BugZero found this defect 158 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 2783439
Consider the following scenario: - You create a table that has a full-text index. - The full-text index fragment is partitioned because it's too large. - You clone the database and then run DBCC CHECKDB to check the clone database. In this scenario, the command fails and the following error 2601 occurs: Msg 2601, Level 14, State 1, Line <LineNumber> Cannot insert duplicate key row in object '<ObjectName>' with unique index '<IndexName>'. The duplicate key value is <KeyValue>.
Last update date:
12/14/2023
Affected products:
SQL Server 2019 on Linux
SQL Server 2019 on Windows
Affected releases:
build lower than 15.0.4345.5
Fixed releases:
15.0.4345.5
Description:
Consider the following scenario: - You create a table that has a full-text index. - The full-text index fragment is partitioned because it's too large. - You clone the database and then run DBCC CHECKDB to check the clone database. In this scenario, the command fails and the following error 2601 occurs: Msg 2601, Level 14, State 1, Line <LineNumber> Cannot insert duplicate key row in object '<ObjectName>' with unique index '<IndexName>'. The duplicate key value is <KeyValue>.
