SQL Server 2016

  1. Too many members have validation errors. For members that display Error in the ValidationStatus column, details are shown ...
  2. Too many tables. The query and the views or functions in it exceed the limit of %1!s! tables. Revise the query to reduce ...
  3. TOPCOUNT=3= , , =The TopCount function returns the first n-item rows of the table expression, ordered in descending order ...
  4. TOPCOUNT=3= Set , Count , Numeric Expression ]=Returns a specified number of items from the topmost members of a specified ...
  5. TOPPERCENT=3= , , =The TopPercent function returns the smallest number of rows in descending order such that the sum of the ...
  6. TOPPERCENT=3= Set , Percentage , Numeric Expression =Sorts a set and returns the topmost elements whose cumulative total ...
  7. TOPSUM=3= , , =The TopSum function returns the smallest number of rows in descending order such that the sum of the rank ...
  8. TOPSUM=3= Set , Value , Numeric Expression =Sorts a set and returns the topmost elements whose cumulative total is at least ...
  9. Total amount of memory available for grants to executing processes. This memory is used primarily for hash, sort and create ...
  10. Total number of cache hits that were unable to build an indexed iterator over the filtered results and had to build a new ...
  11. Total number of evaluation nodes built by MDX execution plans for which the calculations were at the same granularity as ...
  12. Total number of message fragments from the transport that are successfully delivered into local target queues. Note that ...
  13. Total number of messages from local endpoints and the transport that are successfully delivered into local target queues. ...
  14. Total number of messages from the transport that are successfully delivered into local target queues. This includes all messages ...
  15. Total number of requests not executed because of insufficient server resources. This counter represents the number of requests ...
  16. Trace information is still being transferred. If you do not want to wait for all of the information to arrive press Stop. ...
  17. Tracer Tokens measure latency from Publisher to Distributor, Distributor to Subscriber, and the total latency. Click *$*here*$* ...
  18. Traditional-Spanish-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  19. Traditional-Spanish-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  20. Traditional-Spanish-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  21. Traditional-Spanish-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  22. Traditional-Spanish-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  23. Traditional-Spanish-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  24. Traditional-Spanish-100, case-insensitive, accent-sensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  25. Traditional-Spanish-100, case-insensitive, accent-sensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  26. Traditional-Spanish-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  27. Traditional-Spanish-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  28. Traditional-Spanish-100, case-sensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  29. Traditional-Spanish-100, case-sensitive, accent-insensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  30. Traditional-Spanish-100, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  31. Traditional-Spanish-100, case-sensitive, accent-sensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  32. Traditional-Spanish-100, case-sensitive, accent-sensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  33. Training set is too small for the mining model, '%{modelname/}'. The number of training cases should be greater than the ...
  34. Training set is too small for the mining model, '%{modelname/}'. The number of training cases should not be less than ma ...
  35. Transaction %1 ended with a partial command (%2!d!); the next transaction is %3. When troubleshooting, execute DBCC CHECKDB ...
  36. Transaction (Process ID %1!s!) was deadlocked on %2!s! resources with another process and has been chosen as the deadlock ...
  37. Transaction aborted when accessing versioned row in table '%1!s!' in database '%2!s!'. Requested versioned row was not found ...
  38. Transaction aborted when accessing versioned row in table '%1!s!' in database '%2!s!'. Requested versioned row was not found. ...
  39. Transaction cannot be committed because database with name='%{db_name/}', Id='%{db_id/}' is disabled for scoped connections. ...
  40. Transaction cannot be specified when a retained connection is used. This error occurs when Retain is set to TRUE on the connection ...
  41. Transaction Coordination Manager is active with %1!s! as the starting AGE. This is an informational message only. No user ...
  42. Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %1!s!, current ...
  43. Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = {0}, current ...
  44. Transaction count has been changed from %1!s! to %2!s! inside of user defined routine, trigger or aggregate "%3!s!". This ...
  45. Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not ...
  46. Transaction failed in database '%1!s!' because the statement was run under snapshot isolation but the transaction did not ...
  47. Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not ...
  48. Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk ...
  49. Transaction table versions between Vertipaq Table '%{IMBITableName/}' and Tabular Metadata storage encountered unexpected ...
  50. Transaction was aborted as database is moved to read-only mode. This is a temporary situation and please retry the operation. ...
  51. Transactional file system resource manager '%1!s!' failed to recover. For more information, see the accompanying error message, ...
  52. Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%1!s!' ...
  53. TransactionPool contains {0} open transactions, {1} closed transactions, and {2} expired transactions. Ideal total pool size: ...
  54. Transfers a SQL Server database between two instances of SQL Server. Other tasks transfer SQL Server objects only by copying ...
  55. Transfers one or more logins between instances of SQL Server. This task can transfer all logins, only specified logins, or ...
  56. Transfers one or more types of objects between instances of SQL Server. Transfer all objects, all objects of a type, or only ...
  57. Transfers one or more user-defined stored procedures between master databases on instances of SQL Server. Transfer all stored ...
  58. Transfers SQL Server Agent jobs between instances of SQL Server. The Transfer Jobs task can be configured to transfer all ...
  59. Transfers SQL Server user-defined error messages between instances of SQL Server. This task can be configured to transfer ...
  60. Transparent data encryption is currently disabled on this SQL Server PDW. This stored procedure may run only when encryption ...
  61. Transparent Data Encryption is not available in the edition of this SQL Server instance. See books online for more details ...
  62. Transparent data encryption is not enabled on this SQL Server PDW. Server administrator must enable it by using sp_pdw_database_encryption ...
  63. Transparent data encryption is not enabled on this SQL Server PDW. Server administrator must enable it by using sp_pdw_database_encryption ...
  64. Traversal string: (Possible cause of following error: Parameters whose values are supplied positionally (not by name) in ...
  65. Trimester over trimester growth % allows you to view the data for the current period as a percentage of the same period in ...
  66. Trimester over trimester growth allows you to view the difference in the data for the current period and the same period ...
  67. Trimester to date enables you to see data in an accumulated view from the first day of the trimester to the selected period. ...
  68. True if the read-only routing list (READ_ONLY_ROUTING_LIST) is not empty but none of the replicas in the list are available ...
  69. TRUNCATE TABLE statement failed because table '%1!s!' has a columnstore index on it. A table with a columnstore index cannot ...
  70. TRUNCATE TABLE statement failed. Index '%1!s!' is not partitioned, but table '%2!s!' uses partition function '%3!s!'. Index ...
  71. TRUNCATE TABLE statement failed. Index '%1!s!' uses partition function '%2!s!', but table '%3!s!' uses non-equivalent partition ...
  72. Truncation may occur due to inserting data from data flow column "%1!s!" with a length of %2!d! to database column "%3!s!" ...
  73. Truncation may occur due to retrieving data from database column "%1!s!" with a length of %2!d! to data flow column "%3!s!" ...
  74. Trusted connections do not require a login name. You must use the -U option on the command line to specify the login name ...
  75. Trying to access column {0} after accessing column {1} although CommandBehavior.SequentialAccess was specified as a command ...