SQL Server 2008 R2

  1. Create, view, or delete relationships between tables in the PowerPivot window. Before you can manage relationships, at least ...
  2. CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection ...
  3. CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%1!s!'. Try again later. ...
  4. Creates a new mining model based on an existing mining structure, and saves the model in a temporary file. Specifies the ...
  5. Creates a new mining model that is based on an existing mining structure, specifies the algorithm to use for analysis, and ...
  6. Creates a new mining structure on the current instance of Analysis Services and optionally define a percentage of the data ...
  7. Creates a prediction by mapping an existing mining model to an external data source and then filtering the input data by ...
  8. Creates a prediction on a mining model that contains a nested table, by using an external data source that also contains ...
  9. Creates a prediction on a mining model that contains a nested table, by using an external data source that also contains ...
  10. Creates a query that returns information about an existing mining model, or about the patterns and statistics in the data. ...
  11. Creates or upgrades a management data warehouse for storing data collection set results. To configure data collection for ...
  12. Creating a %1!s! index requires that the primary key in the base table satisfy the following restrictions. The maximum number ...
  13. Creating a new database for the users of the Data Mining Add-ins for Office 2007 gives them the freedom to create temporary ...
  14. Creating a UCP on the specified instance of SQL Server will provision the UCP schema, jobs, and policies, and enable the ...
  15. Creating and altering SOAP endpoints will be removed in a future version of SQL Server. Avoid using this feature in new development ...
  16. Creating or altering compressed table '%1!s!' failed because the uncompressed row size would be %2!s!, including %3!s! bytes ...
  17. Creating or altering table '%1!s!' failed because the minimum row size would be %2!s!, including %3!s! bytes of internal ...
  18. Creating publications from heterogeneous data sources is supported only on servers running Microsoft SQL Server 2005 and ...
  19. Creating the SQL Server Browser service with the following parameters: Display Name: '{0}', Service Type: '{1}', Start Type: ...
  20. Creation of a TSQL endpoint will result in the revocation of any 'Public' connect permissions on the '%1!s!' endpoint. If ...
  21. Creation of the full-text index is not available. Check that you have the correct permissions or that full-text catalogs ...
  22. Credentials cannot be used with the FILESTREAM Provider. Remove any credential entries that are associated with this blob ...
  23. Credentials must be specified before the report can be displayed. Enter credentials in the credentials area and click the ...
  24. Croatian, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  25. Croatian, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  26. Cryptographic provider %1!s! '%2!s!' in dll is different from the guid recorded in system catalog for provider with id %3!s!. ...
  27. Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still ...
  28. Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use ...
  29. Cryptographic provider library '%1!s!' loaded into memory. This is an informational message only. No user action is required. ...
  30. CTI violation on Enqueue. The current event timestamp of '{0:o}' is less than the last enqueued CTI timestamp of '{1:o}'. ...
  31. CTI violation on the output of a published stream. The current event timestamp of '{0:o}' is less than the last CTI timestamp ...
  32. Cube attribute binding for property '%{property_name/}' is invalid because the parent dimension has a different source cube ...
  33. Cube attribute binding for property '%{property_name/}' is invalid because the parent dimension has a different source cube. ...
  34. Cube attribute {0} can not be used as a mining structure column because its attribute hierarchy is not enabled. You can enable ...
  35. Cube Wizard has analyzed the relationships between tables in the data source view to identify fact tables and dimensions. ...
  36. CUID column of 6 bytes cannot be added to index "%1!s!" on object %2!s! because row length would exceed the maximum permissible ...
  37. Culture expression '{0}' is not directly supported in a LINQ query. Assign it to a local variable and then use the variable ...
  38. Cumulative I/O performed by this session since it connected ("sys.dm_exec_sessions.reads" plus "sys.dm_exec_sessions.writes") ...
  39. Current number of threads waiting for a latch. These are latch requests that could not be given immediate grants and are ...
  40. Current selection has inconsistent action options. Select one of the options below to apply the same action to the whole ...
  41. Current selection includes areas with the different types of markup. Select one of the options below to set a new markup ...
  42. Current thread is not configured to access SQL Server internal resources and was likely created inside the Common Language ...
  43. Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the ...
  44. Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with ...
  45. Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %1!s! is missing under element. Consider ...
  46. Cursor plan forcing failed because input plan has more than one node with OperationType=%1!s!. Consider using an XML cursor ...
  47. Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch. ...
  48. Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, ...
  49. Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements. ...
  50. Custom rollup formulas, custom member formulas, All member formulas, and custom level formulas are no longer supported as ...
  51. Cyclical forwarding detected for event %1: Event source was '%2' which matches the current forwarding server. The event was ...
  52. Czech, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  53. Czech, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  54. D Path of the DTS package when the package is present in a file.If the path includes file name, then only that file will ...
  55. Danish-Norwegian, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  56. Danish-Norwegian, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  57. Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read". ...
  58. Data access is not allowed in this context. Either the context is a function or method not marked with DataAccessKind.Read ...
  59. Data associated with the key value, '%{name/}', was not used during training and because this, the value is not a valid key. ...
  60. Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. ...
  61. Data conversion failed while converting column "%1!s!" (%2!d!) to column "%3!s!" (%4!d!). The conversion returned status ...
  62. Data could not be retrieved for the subreport, '{0}', located at: {1}. Data is only retrieved during the initial request ...
  63. Data has changed since the Results pane was last retrieved. Do you want to save your changes now? (Optimistic Concurrency ...
  64. Data in filegroup %1!s! is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup ...
  65. Data mapping to column '%1' was already found in the data. Make sure that no two schema definitions map to the same column. ...
  66. Data Migration In order to migrate data, the following prerequisites must be met: The table must be converted and loaded ...
  67. Data Migration is performing required operation to copy data from Oracle database to SQL Server. This may take few moments. ...
  68. Data or literal value could not be converted to the type of the column in the data source, and the provider was unable to ...
  69. Data refresh schedules that specify 'Once' can only be used when all of the data sources are refreshed on the same schedule. ...
  70. Data to be used for the Associate task of the Data Mining Client or the Shopping Basket Table Analysis Tool. You can build ...
  71. Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions ...
  72. Data truncated when converting range values to the partition function parameter type. The range value at ordinal %1!s! requires ...
  73. Data type mapping from '%1!s!' to '%2!s!' does not exist. Review source and destination data type, length, precision, scale, ...
  74. data type, it cannot be migrated using Microsoft OLE DB Provider for Oracle, use Oracle Provider for OLE DB to migrate such ...
  75. Data validation failed for one or more articles. When troubleshooting, check the output log files for any errors that may ...