The Index Allocation Map (IAM) page %1!s! is pointed to by the previous pointer of IAM page %2!s! in object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc unit ID %6!s! (type %7!s!), but it was not detected in the scan.
The index '%1!s!' on table '%2!s!' cannot be disabled because the table has change tracking enabled. Change tracking requires ...
The index '%1!s!' on table '%2!s!' could not be created because the column '%3!s!' in the filter expression of the index ...
The index '{0}' on table '{1}' has {2} column names in index key list. The maximum limit for index or statistics key column ...
The Index Allocation Map (IAM) page %1!s! is pointed to by the next pointer of IAM page %2!s! in object ID %3!s!, index ID ...
The Index Allocation Map (IAM) page %1!s! is pointed to by the previous pointer of IAM page %2!s! in object ID %3!s!, index ...
The index for the primary key '%1!s!.%2!s!' is at least %3!s! bytes. SQL Server supports a maximum key length of %4!s! bytes. ...
The index ID %1!s! on table "%2!s!" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. ...
The index position, %1!d!, is a duplicate. For non-index columns, the index position should be 0. For index columns, the ...
The indexes on table "%1!s!" cannot be reorganized because there is already an online index build or rebuild in progress ...