SQL Server 2016
- The system name '%1!s!' was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying ...
- The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically ...
- The system reports %1!d! percent memory load. There are %2!s! bytes of physical memory with %3!s! bytes free. There are %4!s! ...
- The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary ...
- The T-SQL shown here may not necessarily be the exact T-SQL executed at the server due to any conditional logic you configured ...
- The table "%1!s!" does not appear to be a valid pre-built match index. This error occurs if the metadata record cannot be ...
- The table "{0}" already contains a configuration with name "{1}". Do you want to reuse this configuration or overwrite information ...
- The table "{0}" cannot be used as a source for SQL Server configurations. The column "{1}" does not have the expected data ...
- The table "{0}" cannot be used as a source for SQL Server configurations. This table does not have the necessary columns ...
- The table %1!s! contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it ...
- The table %1!s! does not have a primary key, which is required for transactional replication. Create a primary key on the ...
- The table %1!s!, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized ...
- The table '%1!s!' cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online. ...
- The table '%1!s!' has been created or altered after the start of the current transaction. The transaction was aborted. Please ...
- The table '%1!s!' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular ...
- The table '%1!s!.%2!s!' already appears in a transactional publication on Oracle Gateway Publisher '%3!s!'. When using the ...
- The table '%1!s!.%2!s!' already appears in the transactional publication '%3!s!' on Publisher '%4!s!'. The Oracle Gateway ...
- The table '%{dimname/}' has two relationships with the same ToRelationshipEnd Role name: '%{rolename/}', which is not allowed. ...
- The table '{0}' does not exist in the database '{1}'. Verify spelling of the table and database names and make sure you are ...
- The table above shows only those jobs that are still processing on the report server. To cancel all jobs, click OK. To close ...
- The Table Analysis Tools Add-in for Excel 2010 cannot function without a connection to a SQL Server 2008 (or later) Analysis ...
- The table being loaded into memory has a user-defined data type (' ') that is not recognized. Close all of your open database ...
- The table column '%{IWColumnName/}', in the table '%{IWTableName/}', binds to a column of Binary data type, which is not ...
- The table column '%{IWColumnName/}', in the table '%{IWTableName/}', has the corresponding attribute hierarchy not optimized ...
- The table contains measures, but PowerPivot can't display them. This may be because there are too many measures to display, ...
- The table contains measures, but the designer cannot display them. This may be because there are too many measures to display, ...
- The table definition appears to be missing from the DATATABLE function; the last parameter of the DATATABLE function must ...
- The table has a column with a LOB type, i.e., n]varchar(max) or varbinary(max). COLUMNSTORE indexes are not supported for ...
- The table is linked to an Excel table that is no longer available. The Excel table might have been deleted or renamed. Correcting ...
- The table name '{0}' specified through -Tf switch cannot be parsed successfully. Table name should be specified in format: ...
- The Table or View name is not expected. If you are quoting the table name, please use the prefix %1!s! and the suffix %2!s! ...
- The table or view name is not valid. Please use the table prefix {0} and suffix {1} of the data provider if you are quoting ...
- The table referenced by the PerspectiveTable object '%{persptable/}' in perspective '%{persp/}' cannot be altered. Altering ...
- The table that you selected includes one or more columns of type hierarchyid. Publishing this table for bidirectional replication ...
- The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution ...
- The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. ...
- The table {1}' has rows that contain a different number of cells than the number of the columns in the table (including cells ...
- The table, '%{IWTableName/}', cannot be created in Tabular mode because the column, '%{IWColumnName/}', is associated with ...
- The Table-Valued Parameter column %1!Iu! was bound through multiple accessor bindings. Each Table-Valued Parameter Rowset ...
- The Table-Valued Parameter column %1!Iu! was marked as default and it was also bound through accessor %2!Iu!. Default columns ...
- The Table-Valued Parameter column %1!Iu! was not bound in the same accessor as it's surrounding columns (from %2!Iu! to %3!Iu!). ...
- The Table-Valued Parameter column %1!Iu! was not bound through any accessor binding. Each non-default column must have 1 ...
- The Tabular Data Stream (TDS) version 1!s! of the client library used to open the connection is unsupported or unknown. Please ...
- The Tabular Data Stream (TDS) version 1!s! of the client library used to open the connection is unsupported or unknown. The ...
- The Tabular Data Stream (TDS) version 1!s! of the client library used to recover a dead connection is unsupported or unknown. ...
- The Tabular database '%{DBName/}' is in an inconsistent state and cannot be accessed. Please delete it and recreate it or ...
- The tail of the log for database %1!s! is being rewritten to match the new sector size of %2!s! bytes. %3!s! bytes at offset ...
- The tail of the log for the database "%1!s!" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if ...
- The target '%1!s!' of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT ...
- The target '%1!s!' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested ...
- The target '%1!s!' of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the ...
- The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that ...
- The target database '%1!s!'.'%2!s!' cannot have lower performance level than the source database '%3!s!'.'%4!s!'. Downgrade ...
- The target database ('%1!s!') is in an availability group and currently does not allow read only connections. For more information ...
- The target database ('%1!s!') is in an availability group and is currently accessible for connections when the application ...
- The target database version %1!s! is not supported by the current code version %2!s!. Change target version to a supported ...
- The target database, '%1!s!', is participating in an availability group and is currently not accessible for queries. Either ...
- The Target dimension is based on a mining model built from the Source dimension. The Source dimension must also be included ...
- The target file extension '{0}' does not match the source file extension '{1}'. File extensions of .rdl, .rsds, .odc, .rsd, ...
- The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), ...
- The target server cannot establish an encrypted connection to the master server '%s'. Make sure that the MsxEncryptChannelOptions ...
- The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information ...
- The target table '%1!s!' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause ...
- The target table '%1!s!' of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when ...
- The target table '%1!s!' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, ...
- The target table '%1!s!' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested ...
- The target table '%1!s!' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. ...
- The target table '%1!s!' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found ...
- The target table of the INSERT statement cannot have DEFAULT constraints using the NEXT VALUE FOR function when the FROM ...
- The task has a transaction option of "Required" and connection "%1!s!" is of type "ODBC". ODBC connections don't support ...
- The task providing the custom event "%1!s!" does not allow this event to be handled in the package. The custom event was ...
- The task was not able to detect any key influencers for the '{0}' column. The values of '{0}' seem unrelated to values of ...
- The task was not able to detect any significant patterns for the '{0}' column. Entering more values in the '{0}' column might ...
- The task with the name "{0}" and the creation name "{1}" is not registered for use on this computer. Contact Information: ...
- The TCP-IP port returned to the client in the routing response. The port is determined using the READ_ONLY_ROUTING_URL set ...