| Event Id | 1530 |
| Source | MSSQLServer |
| Description | CREATE INDEX with DROP_EXISTING was aborted because a row was out of order. Most significant offending primary key is %S_KEY. Explicitly drop and create the index instead. |
| Event Information | According To Microsoft: Cause: This error occurs when you try to create an index using the DROP_EXISTING clause of the CREATE INDEX statement on a column or columns containing data that is not in sorted order. When this error occurs, no index is created. The DROP_EXISTING clause speeds the creation of an index when the data in the table is already in order. The space required to build a clustered index is less when the DROP_EXISTING clause is used. The DROP_EXISTING clause speeds index creation only for clustered indexes or unique nonclustered indexes. Creating a nonunique, nonclustered index with the DROP_EXISTING clause may succeed, but there is no improvement in performance. Resolution: Use either of these strategies: Execute CREATE INDEX with the DROP_EXISTING clause. Drop and re-create the index without any clauses. You can also use the SORTED_DATA_REORG clause, which physically reorganizes the data. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 1530 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.