Unique Index Error when creating non-unique index - SQL Server(创建非唯一索引时的唯一索引错误 - SQL Server)
问题描述
我尝试对 SQL Server 2005 中的表创建非唯一索引.尝试创建它时出现以下错误.
I trying to and a non-unique index to a table table in SQL Server 2005. I am getting the following error when I try to create it.
消息 1505,级别 16,状态 1,第 1 行CREATE UNIQUE INDEX 语句终止,因为找到了对象名称dbo.oe_pick_ticket"和索引名称idx_pick_ticket_popup_wmms"的重复键.重复键值为 (1093066, N, N, N, , FBF, 100001, 1074359, 1118930).
Msg 1505, Level 16, State 1, Line 1 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.oe_pick_ticket' and the index name 'idx_pick_ticket_popup_wmms'. The duplicate key value is (1093066, N, N, N, , FBF, 100001, 1074359, 1118930).
我的create语句如下:
My create statement is as follows:
CREATE NONCLUSTERED INDEX idx_pick_ticket_popup_wmms
ON oe_pick_ticket (invoice_no, delete_flag, direct_shipment, auxiliary, oe_pick_ticket_type_cd, company_id, location_id, order_no)
我尝试重建聚集/唯一/主键索引,但没有任何改变.有谁知道我为什么会收到此错误以及如何解决它?
I have tried rebuilding the clustered/unique/primary key index and that didn't change anything. Does anyone know why I am getting this error and how to resolve it?
推荐答案
事实证明,我能够自己解决这个问题.我在桌子上运行了一个 DBCC CHECKTABLE,结果不一致.之后,我使用 REBUILD_REPAIR 选项再次运行它并修复了主键不一致的问题.
It turns out that I was able to figure this out on my own. I ran a DBCC CHECKTABLE on the table and there was an inconsistency. After that I ran it again with the REBUILD_REPAIR option and it fixed the primary key inconsistency.
这篇关于创建非唯一索引时的唯一索引错误 - SQL Server的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:创建非唯一索引时的唯一索引错误 - SQL Server


基础教程推荐
- 将数据从 MS SQL 迁移到 PostgreSQL? 2022-01-01
- 使用pyodbc“不安全"的Python多处理和数据库访问? 2022-01-01
- SQL Server 2016更改对象所有者 2022-01-01
- SQL Server 中单行 MERGE/upsert 的语法 2021-01-01
- 在 VB.NET 中更新 SQL Server DateTime 列 2021-01-01
- 如何在 SQL Server 的嵌套过程中处理事务? 2021-01-01
- SQL Server:只有 GROUP BY 中的最后一个条目 2021-01-01
- 无法在 ubuntu 中启动 mysql 服务器 2021-01-01
- Sql Server 字符串到日期的转换 2021-01-01
- ERROR 2006 (HY000): MySQL 服务器已经消失 2021-01-01