SQL Server 2008

  1. The number of batches that completed successfully per second by the background task that cleans up deferred dropped allocation ...
  2. The number of buckets found by the discretization method is not same as the number of buckets requested by the attribute ...
  3. The number of buffer bytes associated with message fragments being marshalled, or marshalled and ready to be sent with send ...
  4. The number of bytes associated with in completed transport receive I/O operations whose message fragments haven't been enqueued ...
  5. The number of columns captured by capture instance '%1!s!' exceeds the maximum allowed number: %2!s!. Use the @captured_columns_list ...
  6. The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set. ...
  7. The number of columns in the flat file connection manager must be the same as the number of columns in the flat file adapter. ...
  8. The number of columns in the referencing column list for foreign key '%1!s!' does not match those of the primary key in the ...
  9. The number of columns specified in the CHANGETABLE(VERSION .) function does not match the number of primary key columns for ...
  10. The number of concurrent dynamic snapshot sessions has exceeded the specified limit of %1!d!, processing of this snapshot ...
  11. The number of concurrent user connections was reduced to %1!s!, because it exceeded the allowable limit for this edition ...
  12. The number of data or index records at the level of the index. For a heap, this is the number of records in the entire heap. ...
  13. The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation ...
  14. The number of days to keep report execution information in the execution log. Valid values for this property include -1 and ...
  15. The number of default columns (%1!u!) specified for Table-Valued Parameter Rowset exceeds the total number of Table-Valued ...
  16. The number of elements in the source collection is greater than the available space from index to the end of the destination ...
  17. The number of filegroups or range values is not valid. Enter an extra filegroup in addition to the number of boundary values. ...
  18. The number of foreign key bindings for the '%{tablecolumn/}' nested table does not match the number of key bindings for the ...
  19. The number of input and output columns are not equal. The total number of input columns on all inputs must be the same as ...
  20. The number of instances of the outermost column group that can appear to the left of the row headers (or to the right of ...
  21. The number of key columns in the APPEND clause number %d{iClause/} is not the same as the top-level APPEND clause of the ...
  22. The number of keys specified does not match the number of keys required to address this object. The number of keys required ...
  23. The number of message fragments from the transport that are successfully delivered into local target queues per second. Note ...
  24. The number of messages from local endpoints and the transport that are successfully delivered into local target queues per ...
  25. The number of messages from local endpoints that are successfully delivered directly into local target queues per second. ...
  26. The number of messages from the transport that are successfully delivered into local target queues per second. This includes ...
  27. The number of package items in parameter '{0}' is not equal to the number of packages defined in MSI extension metadata '{1}'. ...
  28. The number of parameters in the replication command does not match what is defined in the DTS package. Regenerate the package. ...
  29. The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%1!s!). ...
  30. The number of priority 1 messages from local endpoints and the transport that are successfully delivered into local target ...
  31. The number of priority 10 messages from local endpoints and the transport that are successfully delivered into local target ...
  32. The number of priority 2 messages from local endpoints and the transport that are successfully delivered into local target ...
  33. The number of priority 3 messages from local endpoints and the transport that are successfully delivered into local target ...
  34. The number of priority 4 messages from local endpoints and the transport that are successfully delivered into local target ...
  35. The number of priority 5 messages from local endpoints and the transport that are successfully delivered into local target ...
  36. The number of priority 6 messages from local endpoints and the transport that are successfully delivered into local target ...
  37. The number of priority 7 messages from local endpoints and the transport that are successfully delivered into local target ...
  38. The number of priority 8 messages from local endpoints and the transport that are successfully delivered into local target ...
  39. The number of priority 9 messages from local endpoints and the transport that are successfully delivered into local target ...
  40. The number of rowsets created as a result of aborted online index build operations that are waiting to be dropped by the ...
  41. The number of rowsets per second created as a result of aborted online index build operations that were skipped by the background ...
  42. The number of rowsets per second created as a result of aborted online index build operations that were successfully dropped ...
  43. The number of seconds that must elapse before the Report Server assumes the command failed or took too much time to perform ...
  44. The number of seconds to wait before returning from a failed Report Server Database login attempt. A value of 0 allows for ...
  45. The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %1!s!. This ...
  46. The number of threads required for this pipeline is %1!d!, which is more than the system limit of %2!d!. The pipeline requires ...
  47. The number of times that a leaf page cookie could not be used during an index search since changes happened on the leaf page. ...
  48. The number of times that a tree page cookie could not be used during an index search since changes happened on the parent ...
  49. The number of times the SQL Server has been successfully restarted by SQL Server Agent, since the last SQL Server Agent restart. ...
  50. The number of transport receives I/O per second. Note that a transport receive I/O may contain more than one message fragment. ...
  51. The NumKeyColumns value is not valid. In the %1!s!, the value for the NumKeyColumns custom property must be between 1 and ...
  52. The object '%1!s!'.'%2!s!' is not a valid resource governor classifier user-defined function. A valid classifier user-defined ...
  53. The object '{0}' referenced by the indexed view '{1}' cannot be used as the alternate schema object for article '{2}' because ...
  54. The object '{0}' was created, but an error occurred setting extended properties. Use the object properties dialog to set ...
  55. The object cannot be added because another object with the same name already exists in the collection. Use a different name ...
  56. The object does not implement IDispatch. This error occurs when a property object or properties collection attempts to access ...
  57. The object does not support type information. This occurs when the runtime attempts to get the type information from an object ...
  58. The object ID cannot be changed from '%{strID/}' to '%{strNewID/}' for the '%{name/}' %{typename/}. The object ID cannot ...
  59. The object ID is missing from the object definition of %{strName/}. When a CREATE statement has set the object overwrite ...
  60. The object is in a zombie state. An object may enter a zombie state when either ITransaction::Commit or ITransaction::Abort ...
  61. The object model cannot be used since there is no available session context. This typically occurs because the AdomdServer ...
  62. The object model does not accept the calls from non-server threads. This typically occurs because the AdomdServer object ...
  63. The object name cannot be changed from "%1!s!" to "%2!s!" because another object in the collection already uses that name. ...
  64. The object with ID "{0}" referred by to a ForEachPropertyMapping is not a ForEach Loop container. The offending ForEachPropertyMapping ...
  65. The object with ID of '%{id/}', Name of '%{name/}' is of type '%{typename/}' which does not support the requested operation. ...
  66. The ObjectData element is missing in the XML block of a hosted object. This occurs when the XML parser attempts to locate ...
  67. The objects "%1!s!" and "%2!s!" in the FROM clause have the same exposed names. Use correlation names to distinguish them. ...
  68. The OLAP binding of the '%{column/}' nested table should reference the same cube as the binding of the '%{struct/}' mining ...
  69. The OLAP Cube-based mining structure or model, %{name/}, cannot be processed with out-of-line bindings (e.g. the INSERT INTO ...
  70. The OLE Automation extended stored procedures (XPs) allow Transact-SQL batches, stored procedures, and triggers to reference ...
  71. The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact ...
  72. The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!" because of column "%4!s!". ...
  73. The OLE DB provider "%1!s!" for linked server "%2!s!" could not set the range for table "%3!s!". %4!s!. For possible cause ...
  74. The OLE DB provider "%1!s!" for linked server "%2!s!" does not contain the table "%3!s!". The table either does not exist ...
  75. The OLE DB provider "%1!s!" for linked server "%2!s!" reported a change in schema version between compile time ("%3!s!") ...