SQL Server 2008

  1. In SQL Server 2008, connection strings require a different value for some provider names. The value for the SQL Server Native ...
  2. In SQL Server 2008, global trace flags set by a session take effect in other sessions immediately. Also, some trace flags ...
  3. In SQL Server 2008, Integration Services has changed its application programming interfaces (APIs). To be compatible with ...
  4. In SQL Server 2008, Integration Services uses Visual Studio Tools for Applications (VSTA) as its script environment. In earlier ...
  5. In SQL Server 2008, SQL Server Agent supports multiple proxies. You define these proxies by using a new set of stored procedures. ...
  6. In SQL Server 2008, the Lookup transformation includes additional capabilities, such as the ability to persist and share ...
  7. In SQL Server 2008, xml is a reserved system type. Rename your user-defined xml type either before or after upgrading to ...
  8. In SQL Server Enterprise Manager, choose to have the agent update the subscription "on demand only" in the Pull Subscription ...
  9. In SQL Server Express, Web, or Workgroup, you can run the package that the Import and Export Wizard creates, but cannot save ...
  10. In the '%{detail/}' measure group, the '%{mmdim/}' many-to-many dimension references a missing lookup measure group with ...
  11. In the '%{model/}' mining model, a request to the '%{attribute/}' attribute for marginal statistics failed, because the attribute ...
  12. In the '%{modelname/}' mining model, the MODEL_EXISTENCE_ONLY modeling flag is not allowed in the '%{colname/}' key column. ...
  13. In the '%{parentStruct/}' mining structure, the '%{name/}' column is bound to a database column whose data type is set to ...
  14. In the '%{parentStruct/}' structure, the '%{name/}' column does not contain valid bindings to data and cannot be processed. ...
  15. In the following dialog box, specify how the jobs on the new secondary server instance(s) will connect to the monitor server ...
  16. In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or ...
  17. In the mining model, %{modelname/}, the %{colname/} column must be of a continuous type since the REGRESSOR modeling flag ...
  18. In the query/DML operation involving column set '%1!s!', conversion failed when converting from the data type '%2!s!' to ...
  19. In the query/DML operation involving column set '%1!s!', conversion failed when converting from the data type '%2!s!' to ...
  20. In the text editor below, you can input static text and any number of keywords. A keyword is a special formatted character ...
  21. In the XML content that is supplied for the column set '%1!s!', the '%2!s!' attribute on the element '%3!s!' is not valid. ...
  22. In the XML content that is supplied for the column set '%1!s!', the sqltypes:scale attribute value on the element '%2!s!' ...
  23. In the XML content that is supplied for the column set column '%1!s!', the '%2!s!' attribute value on the element '%3!s!' ...
  24. In the XML content that is supplied for the column set column '%1!s!', the sqlDBType:base64Encoded attribute on the element ...
  25. In the XML content that is supplied for the column set column '%1!s!, the '%2!s!' attribute on the element '%3!s!' is not ...
  26. In the XML content that is supplied for the sparse column set '%1!s!', the '%2!s!' attribute value on the element '%3!s!' ...
  27. In the XML that is supplied for the column set '%1!s!', the element '%2!s!' should reside in the global namespace. Remove ...
  28. In this step of the wizard you will be selecting a particular object or several objects to test. Expand the tree control ...
  29. In this step of the wizard, you can configure settings for the data generator used in object parameters of this test case. ...
  30. In this step of the wizard, you can configure test data used in the test case. You can use existing table data from source ...
  31. In this step of the wizard, you can see and change the test data in tables used in this test case. The Configuration tab ...
  32. Include the Database Engine, the core service for storing, processing and securing data. The Database Engine provides controlled ...
  33. Include the granularity attribute of the time dimension in aggregation designs of measure groups with semi-additive measures, ...
  34. Include the granularity attribute of the time dimension in all the aggregations of measure groups with only semi-additive ...
  35. Includes a set of replication objects for copying data and database objects from one database to one or more other databases. ...
  36. Includes event classes produced by the execution of Microsoft Distributed Transaction Coordinator transactions or by writing ...
  37. Includes event classes produced by the execution of Transact-SQL statements passed to an instance of SQL Server from the ...
  38. Includes event classes that are produced when a lock is acquired, cancelled, released, or has some other action performed ...
  39. Includes event classes that are produced when a SQL Server error or warning is returned; for example, an error during the ...
  40. Includes external error information (for example, error information about report data sources) with the error messages that ...
  41. Includes management and development tools: SQL Server Management Studio, SQL Server Configuration Manager, SQL Server Profiler, ...
  42. Includes Management Studio support for the Database Engine and SQL Server Express, SQL Server command-line utility (SQLCMD), ...
  43. Includes Microsoft Sync Framework, a comprehensive synchronization platform that enables collaboration and offline for applications, ...
  44. Includes Reporting Services, a server-based application for creating, managing, and delivering reports in paper-oriented ...
  45. Includes the designer, runtime, and utilities that enable Integration Services to move, integrate, and transform data between ...
  46. Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %1!s!. ...
  47. Incompatible data types were used with a binary operator. The operand types could not be implicitly cast into compatible ...
  48. Incompatible transaction context was specified for a retained connection. This connection has been established under a different ...
  49. Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%1!s!', database ID '%2!s!' ...
  50. Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR ...
  51. Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for ...
  52. Incorrect output type. The output column "%1!s!" (%2!d!) must have the same data type and metadata as the input column to ...
  53. Incorrect parameters were passed to the CREATE %1!s! statement near '%2!s!'. Validate the statement against the index-creation ...
  54. 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 ...
  55. Incorrect syntax near '%1!s!'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. ...
  56. Incorrect syntax near '%1!s!'. If this is intended to be a common table expression, you need to explicitly terminate the ...
  57. Incorrect syntax near '%1!s!'. You may need to set the compatibility level of the current database to a higher value to enable ...
  58. Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change ...
  59. Incorrect UnPivot metadata. In an UnPivot transform, all input columns with a PivotKeyValue that is set, and are pointing ...
  60. Incorrect validation status value, "%1!lu! ". It must be one of the values found in the DTSValidationStatus enumeration. ...
  61. Index ' ' is used to enforce the full-text key on table ' ' and must be bytes or less. This change will disable full-text ...
  62. Index ' ' is used to enforce the full-text key on table ' ' and must be single-column. This change will disable full-text ...
  63. Index ' ' is used to enforce the full-text key on table ' ' and must be unique. This change will disable full-text indexing ...
  64. Index ' ' is used to enforce the full-text key on table ' ' and must not be null. This change will disable full-text indexing ...
  65. Index ' ' is used to enforce the full-text key on table ' '. Deleting this index will disable full-text indexing for the ...
  66. Index '%1!s!' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds ...
  67. Index '%1!s!' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns ...
  68. Index '%1!s!' could not be created or rebuilt. The key length for this index (%2!s! bytes) exceeds the maximum allowed length ...
  69. 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 ...
  70. Index '%1!s!' was not created. This index has a key length of at least %2!s! bytes. The maximum permissible key length is ...
  71. Index '%1!s!', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified ...
  72. Index '%s' specified in input is invalid for the selected partitioning strategy because it doesnt meet alignment requirements ...
  73. Index cannot be created on computed column '%1!s!' of table '%2!s!' because the underlying object '%3!s!' has a different ...
  74. Index creation operation will use %1!s! KB of memory specified in the advanced sp_configure option "min memory per query ...
  75. indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type ...