SQL Server 2016

  1. The system name '%1!s!' was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying ...
  2. The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically ...
  3. 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! ...
  4. The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary ...
  5. The T-SQL shown here may not necessarily be the exact T-SQL executed at the server due to any conditional logic you configured ...
  6. The table "%1!s!" does not appear to be a valid pre-built match index. This error occurs if the metadata record cannot be ...
  7. The table "{0}" already contains a configuration with name "{1}". Do you want to reuse this configuration or overwrite information ...
  8. The table "{0}" cannot be used as a source for SQL Server configurations. The column "{1}" does not have the expected data ...
  9. The table "{0}" cannot be used as a source for SQL Server configurations. This table does not have the necessary columns ...
  10. The table %1!s! contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it ...
  11. The table %1!s! does not have a primary key, which is required for transactional replication. Create a primary key on the ...
  12. The table %1!s!, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized ...
  13. The table '%1!s!' cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online. ...
  14. The table '%1!s!' has been created or altered after the start of the current transaction. The transaction was aborted. Please ...
  15. 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 ...
  16. The table '%1!s!.%2!s!' already appears in a transactional publication on Oracle Gateway Publisher '%3!s!'. When using the ...
  17. The table '%1!s!.%2!s!' already appears in the transactional publication '%3!s!' on Publisher '%4!s!'. The Oracle Gateway ...
  18. The table '%{dimname/}' has two relationships with the same ToRelationshipEnd Role name: '%{rolename/}', which is not allowed. ...
  19. The table '{0}' does not exist in the database '{1}'. Verify spelling of the table and database names and make sure you are ...
  20. The table above shows only those jobs that are still processing on the report server. To cancel all jobs, click OK. To close ...
  21. The Table Analysis Tools Add-in for Excel 2010 cannot function without a connection to a SQL Server 2008 (or later) Analysis ...
  22. The table being loaded into memory has a user-defined data type (' ') that is not recognized. Close all of your open database ...
  23. The table column '%{IWColumnName/}', in the table '%{IWTableName/}', binds to a column of Binary data type, which is not ...
  24. The table column '%{IWColumnName/}', in the table '%{IWTableName/}', has the corresponding attribute hierarchy not optimized ...
  25. The table contains measures, but PowerPivot can't display them. This may be because there are too many measures to display, ...
  26. The table contains measures, but the designer cannot display them. This may be because there are too many measures to display, ...
  27. The table definition appears to be missing from the DATATABLE function; the last parameter of the DATATABLE function must ...
  28. The table has a column with a LOB type, i.e., n]varchar(max) or varbinary(max). COLUMNSTORE indexes are not supported for ...
  29. The table is linked to an Excel table that is no longer available. The Excel table might have been deleted or renamed. Correcting ...
  30. The table name '{0}' specified through -Tf switch cannot be parsed successfully. Table name should be specified in format: ...
  31. 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! ...
  32. 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 ...
  33. The table referenced by the PerspectiveTable object '%{persptable/}' in perspective '%{persp/}' cannot be altered. Altering ...
  34. The table that you selected includes one or more columns of type hierarchyid. Publishing this table for bidirectional replication ...
  35. 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 ...
  36. The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. ...
  37. The table {1}' has rows that contain a different number of cells than the number of the columns in the table (including cells ...
  38. The table, '%{IWTableName/}', cannot be created in Tabular mode because the column, '%{IWColumnName/}', is associated with ...
  39. The Table-Valued Parameter column %1!Iu! was bound through multiple accessor bindings. Each Table-Valued Parameter Rowset ...
  40. The Table-Valued Parameter column %1!Iu! was marked as default and it was also bound through accessor %2!Iu!. Default columns ...
  41. 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!). ...
  42. The Table-Valued Parameter column %1!Iu! was not bound through any accessor binding. Each non-default column must have 1 ...
  43. The Tabular Data Stream (TDS) version 1!s! of the client library used to open the connection is unsupported or unknown. Please ...
  44. The Tabular Data Stream (TDS) version 1!s! of the client library used to open the connection is unsupported or unknown. The ...
  45. The Tabular Data Stream (TDS) version 1!s! of the client library used to recover a dead connection is unsupported or unknown. ...
  46. The Tabular database '%{DBName/}' is in an inconsistent state and cannot be accessed. Please delete it and recreate it or ...
  47. 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 ...
  48. 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 ...
  49. 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 ...
  50. The target '%1!s!' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested ...
  51. The target '%1!s!' of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the ...
  52. The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that ...
  53. The target database '%1!s!'.'%2!s!' cannot have lower performance level than the source database '%3!s!'.'%4!s!'. Downgrade ...
  54. The target database ('%1!s!') is in an availability group and currently does not allow read only connections. For more information ...
  55. The target database ('%1!s!') is in an availability group and is currently accessible for connections when the application ...
  56. The target database version %1!s! is not supported by the current code version %2!s!. Change target version to a supported ...
  57. The target database, '%1!s!', is participating in an availability group and is currently not accessible for queries. Either ...
  58. The Target dimension is based on a mining model built from the Source dimension. The Source dimension must also be included ...
  59. The target file extension '{0}' does not match the source file extension '{1}'. File extensions of .rdl, .rsds, .odc, .rsd, ...
  60. The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), ...
  61. The target server cannot establish an encrypted connection to the master server '%s'. Make sure that the MsxEncryptChannelOptions ...
  62. The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information ...
  63. The target table '%1!s!' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause ...
  64. The target table '%1!s!' of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when ...
  65. The target table '%1!s!' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, ...
  66. The target table '%1!s!' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested ...
  67. The target table '%1!s!' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. ...
  68. The target table '%1!s!' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found ...
  69. The target table of the INSERT statement cannot have DEFAULT constraints using the NEXT VALUE FOR function when the FROM ...
  70. The task has a transaction option of "Required" and connection "%1!s!" is of type "ODBC". ODBC connections don't support ...
  71. The task providing the custom event "%1!s!" does not allow this event to be handled in the package. The custom event was ...
  72. The task was not able to detect any key influencers for the '{0}' column. The values of '{0}' seem unrelated to values of ...
  73. The task was not able to detect any significant patterns for the '{0}' column. Entering more values in the '{0}' column might ...
  74. The task with the name "{0}" and the creation name "{1}" is not registered for use on this computer. Contact Information: ...
  75. The TCP-IP port returned to the client in the routing response. The port is determined using the READ_ONLY_ROUTING_URL set ...