SQL Server 2016

  1. The TempFilePath property is not specified and the environment variable TEMP is not set. Unable to create temporary files. ...
  2. The Term Extraction transformation is unable to process the input text because a sentence from the input text is too long. ...
  3. The terms used for spatial data types should not be used as names for either common language runtime (CLR) or alias UDTs. ...
  4. The test connection failed because the provider could not be initialized. If you contact Microsoft support about this error, ...
  5. The TEXT IN ROW feature will be removed in a future version of SQL Server. Avoid using sp_tableoption for TEXT IN ROW option ...
  6. The text label for the report item, which is used for purposes such as rendering TITLE and ALT attributes in HTML reports. ...
  7. The text that you have selected cannot be represented graphically using the Query Designer. Please select just the text necessary ...
  8. The text you want to find. Use double quotes (empty text) to match the first character in within_text; wildcard characters ...
  9. The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development ...
  10. The TextData filter will not be applied for RPC events because the TextData event column is not selected. Do you want to ...
  11. The third argument of the Descendants function must be one of the following: SELF, BEFORE, AFTER, SELF_AND_BEFORE, SELF_AND_AFTER, ...
  12. The third argument to the CROSSFILTER function should be 0 for None or 1 for OneWay, or 2 for Both. It is also possible to ...
  13. The third parameter for table option 'text in row' is invalid. It should be 'on', 'off', '0', '1' or a number from 24 through ...
  14. The third-party algorithm you have selected cannot be deployed to the destination server. The destination server is running ...
  15. The thread for the SSIS Bulk Insert is no longer running. No more rows can be inserted. Try increasing the bulk insert thread ...
  16. The thread pool for Always On Availability Groups was unable to start a new worker thread because there are not enough available ...
  17. The threshold %1!s!:%2!s! for the publication %3!s! has been set. Make sure that the logreader and distribution agents are ...
  18. The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying ...
  19. The time (in seconds) that the message has been alive. When this value is greater than or equal to the time_to_live field ...
  20. The time dimension in the relevant measure group is parent-child type and there is a semiadditive measure '%{name/}' in the ...
  21. The time intervals over which query performance is to be observed. History contains the baseline interval. Recent contains ...
  22. The time series Key Time column has a data type that is not valid. A Key Time column must have a numeric or date/time/timestamp ...
  23. The time series prediction for the '%{modelname/}' model adds new data, but the start time for the prediction occurs before ...
  24. The time spent between writing the federated authenticaion information token and receiving the federated authentication token ...
  25. The time-out value provided is not valid. Specify the number of seconds that the task allows the process to run. The minimum ...
  26. The time-out was exceeded while the server waited for a response from SQL Server Agent. Make sure that the SQL Server Agent ...
  27. The timezone provided to builtin function %1!s! would cause the datetimeoffset to overflow the range of valid date range ...
  28. The TOP operator can return a maximum of %1!s! sorted rows. %2!s! was requested. Reduce the number of rows selected or simplify ...
  29. The TopCount function returns the first n-item rows of the table expression, ordered in descending order by the rank expression. ...
  30. The topic %1!s! is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp ...
  31. The topology configuration has changed. The new configuration requires that you quiesce all nodes in the topology. For more ...
  32. The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology. ...
  33. The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all ...
  34. The topology view is not available when connected to '{0}'. To configure the topology, manually add the required nodes and ...
  35. The TopPercent function returns the smallest number of rows in descending order such that the sum of the rank expression ...
  36. The TopSum function returns the smallest number of rows in descending order such that the sum of the rank expression values ...
  37. The total number of keybindings of the linked %{typename/}, with the ID of '%{id/}', Name of '%{name/}' on the remote server ...
  38. The total number of locks that were converted. These locks are deallocated because they are covered by the escalated lock. ...
  39. The total number of pages in the current continous page sequence. The number can be reset by using page breaks. Can be used ...
  40. The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover ...
  41. The trace flag {0} is already active. Drop the existing diagnostic session that enabled the trace flag and retry the request. ...
  42. The trace log cannot be found at the default directory location. Trace logs will be created at the following location: %1 ...
  43. The trace log cannot be found at the default directory location. Trace logs will be created at the following location: %1 ...
  44. The tracer token ID (%1!s!) could not be found for Publisher %2!s!, database %3!s!, publication %4!s!. Use the stored procedure ...
  45. The transaction cannot be assigned because the connection object associated with the transaction and the connection object ...
  46. The transaction cannot be reversed. Either this transaction type cannot be reversed or a related transaction must be reversed ...
  47. The Transaction Coordination Manager has encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This ...
  48. The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may ...
  49. The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. ...
  50. The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated. ...
  51. The transaction for posting merge snapshot commands to the Publisher database had been chosen as a deadlock victim, the operation ...
  52. The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same ...
  53. The transaction log contains a record (logop %1!s!) that is not valid. The log has been corrupted. Restore the database from ...
  54. The transaction outcome. This will be true if the resolution was to commit the transaction or false if the resolution was ...
  55. The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction. ...
  56. The transaction was terminated because of the availability replica config/state change or because ghost records are being ...
  57. The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at ...
  58. The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable ...
  59. The translation for culture '%{culture/}' references an object of type '%{typename/}' with ID %{id/} but that object cannot ...
  60. The translation for culture '%{culture/}' references an object of type '%{typename/}' with name '%{name/}' but that object ...
  61. The translation for object of type '%{typename/}' with name '%{name/}' for culture '%{culture/}' does not specify a property. ...
  62. The transmission queue row with conversation handle '%1!s!' and message sequence number %2!s! references a missing multicast ...
  63. The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream. ...
  64. The transport subscriber failed to process the build secondary replica event (partition ID %1!s!). If this condition persists, ...
  65. The transport subscriber failed to process the configuration change replica event (partition ID %1!s!). If this condition ...
  66. The TransSubscription.BackupInformation property must be set with valid backup information when creating a subscription with ...
  67. The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are ...
  68. The True/False expression does not specify a column. Each True/False expressions used as a table filter expression must refer ...
  69. The TSQL debugger has not been installed properly on the Visual Studio machine (ssdebugps.dll may not be registered properly). ...
  70. The tuple at index '%ld{tuple/}' from the table definition of the DATATABLE function appears to be incorrect; the tuples ...
  71. The tuple at index '%ld{tuple/}' from the table definition of the DATATABLE function does not have a constant expression ...
  72. The tuple at index '%ld{tuple/}' from the table definition of the DATATABLE function does not have the expected number of ...
  73. The type '{0}' appears in two structurally incompatible initializations within a single LINQ to Entities query. A type can ...
  74. The type '{0}' doesn't have any key members. A RelationshipType or EntityType must either have key members or a BaseType ...
  75. The type '{0}' in the assembly '{1}' is attributed as a operation instance type, but it does not implement the IOperationInstance ...