SQL Server 2008 R2

  1. Includes event classes produced by the execution of Transact-SQL statements passed to an instance of SQL Server from the ...
  2. Includes event classes that are produced when a lock is acquired, cancelled, released, or has some other action performed ...
  3. Includes event classes that are produced when a SQL Server error or warning is returned; for example, an error during the ...
  4. Includes external error information (for example, error information about report data sources) with the error messages that ...
  5. Includes management and development tools: SQL Server Management Studio, SQL Server Configuration Manager, SQL Server Profiler, ...
  6. Includes Management Studio support for the Database Engine and SQL Server Express, SQL Server command-line utility (SQLCMD), ...
  7. Includes Microsoft Sync Framework, a comprehensive synchronization platform that enables collaboration and offline for applications, ...
  8. Includes Reporting Services, a server-based application for creating, managing, and delivering reports in paper-oriented ...
  9. Includes the Database Engine, the core service for storing, processing and securing data. The Database Engine provides controlled ...
  10. Includes the Database Engine, the core service for storing, processing and securing data. The Database Engine provides controlled ...
  11. Includes the designer, runtime, and utilities that enable Integration Services to move, integrate, and transform data between ...
  12. Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %1!s!. ...
  13. Incompatible data types were used with a binary operator. The operand types could not be implicitly cast into compatible ...
  14. Incompatible transaction context was specified for a retained connection. This connection has been established under a different ...
  15. Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%1!s!', database ID '%2!s!' ...
  16. Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR ...
  17. Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for ...
  18. Incorrect output type. The output column "%1!s!" (%2!d!) must have the same data type and metadata as the input column to ...
  19. Incorrect parameters were passed to the CREATE %1!s! statement near '%2!s!'. Validate the statement against the index-creation ...
  20. Incorrect PFS free space information for page %1!s! in object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID ...
  21. Incorrect syntax near '%1!s!'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. ...
  22. Incorrect syntax near '%1!s!'. If this is intended to be a common table expression, you need to explicitly terminate the ...
  23. Incorrect syntax near '%1!s!'. You may need to set the compatibility level of the current database to a higher value to enable ...
  24. Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change ...
  25. Incorrect UnPivot metadata. In an UnPivot transform, all input columns with a PivotKeyValue that is set, and are pointing ...
  26. Incorrect validation status value, "%1!lu! ". It must be one of the values found in the DTSValidationStatus enumeration. ...
  27. Index "%1!s!" on table "%2!s!" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. ...
  28. Index ' ' is used to enforce the full-text key on table ' ' and must be bytes or less. This change will disable full-text ...
  29. Index ' ' is used to enforce the full-text key on table ' ' and must be single-column. This change will disable full-text ...
  30. Index ' ' is used to enforce the full-text key on table ' ' and must be unique. This change will disable full-text indexing ...
  31. Index ' ' is used to enforce the full-text key on table ' ' and must not be null. This change will disable full-text indexing ...
  32. Index ' ' is used to enforce the full-text key on table ' '. Deleting this index will disable full-text indexing for the ...
  33. Index '%1!s!' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds ...
  34. Index '%1!s!' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns ...
  35. Index '%1!s!' could not be created or rebuilt. The key length for this index (%2!s! bytes) exceeds the maximum allowed length ...
  36. Index '%1!s!' must be either a primary key or a unique index for table '%2!s!.%3!s!'. Specify an index that meets at least ...
  37. Index '%1!s!' was not created. This index has a key length of at least %2!s! bytes. The maximum permissible key length is ...
  38. Index '%1!s!', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified ...
  39. Index '%s' specified in input is invalid for the selected partitioning strategy because it doesnt meet alignment requirements ...
  40. Index '{0}' is a spatial index. User-defined functions with a spatial index are not supported in a data-tier application. ...
  41. Index '{0}' is a spatial index. User-defined table types with a spatial index are not supported in a data-tier application. ...
  42. Index cannot be created on computed column '%1!s!' of table '%2!s!' because the underlying object '%3!s!' has a different ...
  43. Index creation operation will use %1!s! KB of memory specified in the advanced sp_configure option "min memory per query ...
  44. indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type ...
  45. Indexed views are supported only in the Enterprise Edition of Microsoft SQL Server 2000 or later. You have published one ...
  46. INDEXKEY_PROPERTY will be removed in a future version of SQL Server. Avoid using this feature in new development work, and ...
  47. Indicates a poison message was detected because there were five transaction rollbacks in a row on a Service Broker queue. ...
  48. Indicates an object has been altered (for example, by ALTER INDEX, ALTER TABLE, or ALTER DATABASE statements). Each DDL operation ...
  49. Indicates properties of existing user connections when trace was started. Server fires one ExistingConnection event per user ...
  50. Indicates sort operations that do not fit into memory. Does not include sort operations involving the creation of indexes, ...
  51. Indicates that a BEGIN TRANSACTION request has been completed. The request was sent from the client through Transaction Management ...
  52. Indicates that a BEGIN TRANSACTION request is starting. The request was sent from the client through Transaction Management ...
  53. Indicates that a COMMIT TRANSACTION request completed. The request was sent from the client through Transaction Management ...
  54. Indicates that a COMMIT TRANSACTION request is starting. The request was sent from the client through Transaction Management ...
  55. Indicates that a full-text crawl (population) has started. Use this event class to check if a crawl request is actually being ...
  56. Indicates that a full-text crawl (population) has stopped. The stop could due to a successfully completed crawl or a fatal ...
  57. Indicates that a lock on a resource, such as a data page, has been released. The Lock:Acquired and Lock:Released event classes ...
  58. Indicates that a predicate joining two tables is not present. This can potentially result in long-running queries or inaccurate ...
  59. Indicates that a predicate joining two tables is not present. This can potentially result in long-running queries or inaccurate ...
  60. Indicates that a PROMOTE TRANSACTION request has completed. The request was sent from the client through Transaction Management ...
  61. Indicates that a PROMOTE TRANSACTION request is starting. The request was sent from the client through Transaction Management ...
  62. Indicates that a request for a lock on a resource, such as a page, has timed out due to another transaction holding a blocking ...
  63. Indicates that a request for a lock on a resource, such as a page, has timed out due to another transaction holding a blocking ...
  64. Indicates that a ROLLBACK TRANSACTION request completed. The request was sent from the client through Transaction Management ...
  65. Indicates that a ROLLBACK TRANSACTION request is starting. The request was sent from the client through Transaction Management ...
  66. Indicates that a SAVE TRANSACTION request has completed. The request was sent from the client through Transaction Management ...
  67. Indicates that a SAVE TRANSACTION request is starting. The request was sent from the client through Transaction Management ...
  68. Indicates that a task has been blocked for more than a specified amount of time. This event class does not include system ...
  69. Indicates that acquisition of a lock on a resource, such as a data page, has been achieved. The Lock:Acquired and Lock:Released ...
  70. Indicates that all legend items are shown in reversed order. This property only affects legend items automatically added ...
  71. Indicates that an exception has been encountered during a full-text crawl. The error will usually cause the full-text crawl ...
  72. Indicates that column statistics which would have been useful to the query optimizer are not present. This can cause the ...
  73. Indicates that errors have occurred in the Service Broker Transport layer. The error number and state values indicate the ...
  74. Indicates that report should be written to a file. If a file name is supplied, the reports will be written to that destination, ...
  75. Indicates that SQL Server could not produce an execution plan for a query or batch that contained a plan guide. SQL Server ...