SQL Server 2016
- Synchronize failed as source server is set to work in Tabular mode and target server is set to work in Multidimensional mode. ...
- Synchronizes Report Server files (.rdl, .rsds, .smdl, .rsd, .rsc, .rdlx) from a SharePoint document library to the report ...
- System administrator accounts cannot be specified when adding a brick to a matrix. Remove the command prompt parameter {0}, ...
- System CPU delayed for all requests in the specified instance of the performance object as a percentage of the total time ...
- System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active. ...
- System process ID %1!s! tried to terminate the distributed transaction with Unit of Work ID %2!s!. This message occurs when ...
- System table '%1!s!' (object ID %2!s!, index ID %3!s!) is in filegroup %4!s!. All system tables must be in filegroup %5!s!. ...
- System table pre-checks: Object ID %1!s! has chain linkage mismatch. %2!s!->next = %3!s!, but %4!s!->prev = %5!s!. Check ...
- System table pre-checks: Object ID %1!s! has cross-object chain linkage. Page %2!s! points to %3!s! in alloc unit ID %4!s! ...
- System table pre-checks: Object ID %1!s!. Could not read and latch page %2!s! with latch type %3!s!. Check statement terminated ...
- System table pre-checks: Object ID %1!s!. Loop in data chain detected at %2!s!. Check statement terminated due to unrepairable ...
- System table pre-checks: Object ID %1!s!. Page %2!s! has unexpected page type %3!s!. Check statement terminated due to unrepairable ...
- System views related to Windows Fabric partitions and replicas are not available at this time, because replica manager has ...
- System-versioned table schema modification failed because adding computed column while system-versioning is ON is not supported. ...
- System-versioned table schema modification failed because column '%1!s!' at ordinal %2!s! in history table '%3!s!' has a ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same ANSI trimming semantics in ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same collation in tables '%2!s!' ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same column set property in tables ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same masking functions in tables ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same nullability attribute in ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same sparse storage attribute ...
- System-versioned table schema modification failed because column '%1!s!' does not have the same XML Schema Collection in ...
- System-versioned table schema modification failed because column '%1!s!' does not use identical encryption in tables '%2!s!' ...
- System-versioned table schema modification failed because column '%1!s!' has data type %2!s! in history table '%3!s!' which ...
- System-versioned table schema modification failed because column '%1!s!' in history table '%2!s!' corresponds to a generated ...
- System-versioned table schema modification failed because history table '%1!s!' has computed column specification. Consider ...
- System-versioned table schema modification failed because history table '%1!s!' has custom unique keys defined. Consider ...
- System-versioned table schema modification failed because history table '%1!s!' has foreign keys defined. Consider dropping ...
- System-versioned table schema modification failed because history table '%1!s!' has IDENTITY column specification. Consider ...
- System-versioned table schema modification failed because history table '%1!s!' has ROWGUID column specification. Consider ...
- System-versioned table schema modification failed because history table '%1!s!' has table or column constraints defined. ...
- System-versioned table schema modification failed because history table '%1!s!' has triggers defined. Consider dropping all ...
- System-versioned table schema modification failed because history table '%1!s!' is configured for change data capture. Consider ...
- System-versioned table schema modification failed because history table '%1!s!' is not available or it is placed on a read-only ...
- System-versioned table schema modification failed because online alter is not supported on system-versioned memory optimized ...
- System-versioned table schema modification failed because system column '%1!s!' in history table '%2!s!' corresponds to a ...
- System-versioned table schema modification failed because table '%1!s!' has %2!s! columns and table '%3!s!' has %4!s! columns. ...
- System-versioned table SYSTEM_TIME period definition end column name not matching 'GENERATED ALWAYS AS ROW END' column name. ...
- System-versioned table SYSTEM_TIME period definition start column name not matching 'GENERATED ALWAYS AS ROW START' column ...
- Systematically create and register a data-tier application from an existing user database on a UCP enrolled instance of SQL ...
- Table "%1!s!" does not have any records for configuration. This occurs when configuring from a SQL Server table that has ...
- Table %1!s! contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter ...
- Table %1!s! has a partition key already. Explicitly specifying a new partition key is not allowed. Please use "Alter table". ...
- Table '%1!s!' can not be replicated because it contains imprecise Primary Key column, please recreate table without 'persisted' ...
- Table '%1!s!' cannot be a target of an update or delete statement because it has both the REMOTE_DATA_ARCHIVE option enabled ...
- Table '%1!s!' cannot be a target of an update or delete statement because it has the REMOTE_DATA_ARCHIVE option enabled without ...
- Table '%1!s!' cannot be a target of an update or delete statement through a CURSOR because it has the REMOTE_DATA_ARCHIVE ...
- Table '%1!s!' cannot be a target of an update or delete statement with a FROM clause because it has the REMOTE_DATA_ARCHIVE ...
- Table '%1!s!' cannot be a target of an update or delete statement with an OUTPUT clause because it has the REMOTE_DATA_ARCHIVE ...
- Table '%1!s!' cannot be accessed in SNAPSHOT transaction isolation level because it has REMOTE_DATA_ARCHIVE option enabled. ...
- Table '%1!s!' cannot be the target of an update or delete statement through a view because it has the REMOTE_DATA_ARCHIVE ...
- Table '%1!s!' cannot be used in READTEXT, WRITETEXT and UPDATETEXT statements because it has REMOTE_DATA_ARCHIVE option enabled. ...
- Table '%1!s!' cannot have table '%2!s!' as a parent in a logical record relationship because it already has a different parent ...
- Table '%1!s!' does not have a clustered primary key as required by the %2!s! index. Make sure that the primary key column ...
- Table '%1!s!' foreign key 'originating_server_id' does not have a matching value in the referenced view 'dbo.sysoriginatingservers_view'. ...
- Table '%1!s!' in database '%2!s!' is subscribing to transactional queued publication and published for merge for uploading ...
- Table '%1!s!' into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process ...
- Table '%1!s!' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for ...
- Table '%1!s!' is memory optimized. Only security policies with schema binding enabled may specify security predicates for ...
- Table '%1!s!' may be out of synchronization. Rowcounts (actual: %2!s!, expected: %3!s!). Rowcount method %4!s! used (0 = ...
- Table '%1!s!' might be out of synchronization. Rowcounts (actual: %2!s!, expected %3!s!). Checksum values (actual: %4!s!, ...
- Table '%1!s!' needs to have a clustered primary key with less than %2!s! columns in it in order to create a primary XML index ...
- Table '%1!s!' needs to have a clustered primary key with less than %2!s! columns in it in order to create a selective XML ...
- Table '%1!s!' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically. ...
- Table '%1!s!' uses a clustered columnstore index. Columnstore indexes are not supported in this service tier of the database. ...
- Table '%1!s!' will not be available during reorganizing index '%2!s!'. This is because the index reorganization operation ...
- Table '%1!s!'. Scan count %2!s!, logical reads %3!s!, physical reads %4!s!, read-ahead reads %5!s!, lob logical reads %6!s!, ...
- Table '%{table/}' already has a relationship where Security Filtering Behavior is set to Both. Only one relationship per ...
- Table '%{table/}' cannot be queried in DirectQuery mode because it is based on multiple DSVs. Tables that get data from multiple ...
- Table '%{table/}' does not have a partition with DirectQueryUsage property set to DirectQueryOnly or InMemoryWithDirectQuery. ...
- Table '%{Table/}' has no partition objects in xmsrv.dll structures. Most likely we are asked to process a PowerPivot file ...
- Table '%{table/}' includes multiple partitions with DirectQueryUsage property set to DirectQueryOnly or InMemoryWithDirectQuery. ...
- Table '%{table/}' is configured for row-level security, introducing constraints on how security filters are specified. The ...
- Table '%{table/}' is not based on the same Data Source as other tables in the model. When querying in DirectQuery Mode all ...