SQL Server 2016
- Table '%{table/}' must have ShowAsVariationOnly property set to '1', because it is a target of variation '%{variation/}' ...
- Table '%{table/}' with ShowAsVariationOnly property set to '1' must be a target of a variation when variation notation is ...
- Table '{0}' is no longer filtered, and an unfiltered table does not create partitions of its published data at Subscribers. ...
- table cannot be used as a nested table because it does not have a many-to-one relationship with the case table. You need ...
- Table cannot be used as target of an update or delete operation that involves metadata or security built-in functions. Modify ...
- Table does not have any column that can be used as index key columns; all columns are using LOB types (varchar(max), nvarchar(max), ...
- Table error: %1!s! page %2!s! (object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc unit ID %6!s! (type %7!s!)) is ...
- Table error: A FILESTREAM directory ID %1!s! exists for a column of object ID %2!s!, index ID %3!s!, partition ID %4!s!, ...
- Table error: A FILESTREAM directory ID %1!s! exists for a partition, but the corresponding partition does not exist in the ...
- Table error: alloc unit ID %1!s!, page %2!s! contains an incorrect page ID in its page header. The PageId in the page header ...
- Table error: Allocation page %1!s! has invalid %2!s! page header values. Type is %3!s!. Check type, alloc unit ID and page ...
- Table error: Cannot find the FILESTREAM file "%1!s!" for column ID %2!s! (column directory ID %3!s! container ID %4!s!) in ...
- Table error: Could not check object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) due to ...
- Table error: Cross object linkage. Page %1!s!->next in object ID %2!s!, index ID %3!s!, partition ID %4!s!, AU ID %5!s! (type ...
- Table error: Cross object linkage: Page %1!s!, slot %2!s!, in object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc ...
- Table error: Cross object linkage: Parent page %1!s!, slot %2!s! in object %3!s!, index %4!s!, partition %5!s!, AU %6!s! ...
- Table error: Extent %1!s! in object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) is beyond ...
- Table error: IAM chain linkage error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). ...
- Table error: IAM page %1!s! for object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) is ...
- Table error: Multiple IAM pages for object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) ...
- Table error: Object ID %1!s! has inconsistent metadata. This error cannot be repaired and prevents further processing of ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s! processing encountered file name "%4!s!" twice in the column ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s! processing encountered file name "%4!s!" twice in the column ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) B-tree level mismatch, ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) B-tree level mismatch, ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) contains an anti-matter ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!, row %7!s!. ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!, row %7!s!. ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. %7!s! is ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. Test (%7!s!) ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. Test (%7!s!) ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. Test (%7!s!) ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. Test (%7!s!) ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. Test (%7!s!) ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!. The header ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page (%6!s!:%7!s!), row ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page ID %6!s! contains ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). B-tree chain linkage ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). B-tree page %6!s! has ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Duplicate keys on page ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Index node page %6!s!, ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Keys out of order on ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Page %6!s! is missing ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Page %6!s! is missing ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Page %6!s! was not seen ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Page %6!s!, slot %7!s!, ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). Parent node for page ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The high key value on ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The low key value on ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The next pointer of %6!s! ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The off-row data node ...
- Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). The previous link %6!s! ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, database fragment ID %4!s!. The row on page (%5!s!:%6!s!), ...
- Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!. A row should be on partition number %4!s! but was found ...
- Table error: page %1!s! allocated to object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) ...
- Table error: Page %1!s! is empty in object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!). ...
- Table error: Page %1!s!, Object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!). Unexpected ...
- Table error: page %1!s!, whose header indicates that it is allocated to object ID %2!s!, index ID %3!s!, partition ID %4!s!, ...
- Table error: table '%1!s!' (ID %2!s!). Data row does not have a matching index row in the index '%3!s!' (ID %4!s!). Possible ...
- Table error: table '%1!s!' (ID %2!s!). Index row in index '%3!s!' (ID %4!s!) does not match any data row. Possible extra ...
- Table error: The directory "%1!s!" under the rowset directory ID %2!s! is not a valid FILESTREAM directory in container ID ...
- Table error: The FILESTREAM directory ID %1!s! exists for column ID %2!s! of object ID %3!s!, index ID %4!s!, partition ID ...
- Table error: The FILESTREAM directory ID %1!s! for object ID %2!s!, index ID %3!s!, partition ID %4!s! is in filegroup %5!s!, ...
- Table error: The FILESTREAM file "%1!s!" for column ID %2!s! was found in column directory ID %3!s! of container ID %4!s! ...
- Table error: The orphaned file "%1!s!" was found in the FILESTREAM directory ID %2!s! container ID %3!s! for object ID %4!s!, ...
- Table hints must be removed from the definitions of indexed views. Regardless of which compatibility mode is used, we recommend ...
- Table name '%{IWTableName/}' cannot be created, when in Tabular mode because it specifies multiple collation or language ...
- Table partitioning scheme information will not be scripted for article '{0}' because the partition scheme references the ...
- Table types cannot be used as column types in OPENJSON function with explicit schema. This type is not supported in WITH ...
- Table versions between Vertipaq Table '%{IMBITableName/}' and Tabular Metadata storage encountered unexpected inconsistencies ...