SQL Server 2008 R2

  1. The database '%1!s!' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' ...
  2. The database '%1!s!' cannot be opened because it is version %2!s!. This server supports version %3!s! and earlier. A downgrade ...
  3. The database '%1!s!' is enabled for database mirroring. Database mirroring must be removed before you drop the database. ...
  4. The database '%1!s!' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the ...
  5. The database '{0}' does not exist or is not available on the server '{1}'. Verify spelling of the database name and make ...
  6. The database , '%{Database/}', contains no Impersonation mode or an ImpersonationMode that is not supported for processing ...
  7. The database can not be brought online because file '%1!s!' is currently restored to LSN %2!s! but must be restored to LSN ...
  8. The database can not be created or altered as its definition contains circular dependency between regular and linked cubes. ...
  9. The database cannot be attached because an error occurred while loading the detach log from the file '%1'. One possible reason ...
  10. The database cannot be attached because an error occurred while loading the detach log from the file '%{db_detach_log/}'. ...
  11. The database cannot be attached because an error occurred while loading the detach log from the file '%{filename/}'. One ...
  12. The database cannot be attached because an error occurred while loading the detach log from the file '%{strRef/}'. One possible ...
  13. The database cannot be attached because it was detached from a server with ConnStringEncryptionEnabled=%d{BLSet/} and the ...
  14. The database cannot be attached because it was detached from a server with EnableCompression=%d{BLSet/} and the current server ...
  15. The database cannot be attached because it was detached from a server with EnableXMLMetadata=%d{BLSet/} and the current server ...
  16. The database cannot be attached because the detach log is corrupted. An error occurred when locating or processing the node ...
  17. The database configuration requires a newer version of the client library ({1}). The current library is ({0}). Install the ...
  18. The database connections has been changed from the original project settings. Your metabase is different from underlying ...
  19. The Database E-mail feature is not turned on for this SQL Server instance. To turn on the feature and create a new database ...
  20. The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not ...
  21. The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. ...
  22. The Database Engine received a floating point exception from the operating system while processing a user request. Try the ...
  23. The Database Engine service could not resolve the specified file location. Either the location does not exist, or the current ...
  24. The Database Engine service could not resolve the specified folder location. Either the location does not exist, or the current ...
  25. The database folder '%{detach_log_location/}' does not exist, is too long, or contains characters that are not valid or are ...
  26. The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY ...
  27. The Database ID %1!s!, Page %2!s!, slot %3!s! for LOB data type node does not exist. This is usually caused by transactions ...
  28. The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach ...
  29. The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed. ...
  30. The database is not valid due to the following errors: {0} Aggregation can only be designed for a valid database. Please ...
  31. The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the ...
  32. The database maintenance plan {0} contains log shipping settings. Those settings were not migrated to the new maintenance ...
  33. The database management system (DBMS) %1!s! %2!s! does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms. ...
  34. The database mirroring safety level must be FULL to manually failover database "%1!s!". Set safety level to FULL and retry. ...
  35. The database mirroring service cannot be forced for database "%1!s!" because the database is not in the correct state to ...
  36. The database name is missing. To add the name, right click on the Project name, select Properties, and then enter a database ...
  37. The database owner SID recorded in the master database differs from the database owner SID recorded in database '%1!s!'. ...
  38. The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. Remote service ...
  39. The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. This is a special ...
  40. The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot ...
  41. The Database Publishing Wizard allows you to generate scripts for databases and objects inside of databases. This wizard ...
  42. The database schema requires a newer version of the client library ({1}). The current library is ({0}). Install the required ...
  43. The database schema version for the FILESTREAM blob store is . This version is earlier than version , which is the minimum ...
  44. The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the ...
  45. The database to be restored was named '%1!s!'. Reissue the statement using the WITH REPLACE option to overwrite the '%2!s!' ...
  46. The database was backed up on a server running version %1!s!. That version is incompatible with this server, which is running ...
  47. The database with ID '%{dbid/}' cannot be altered from ReadWrite to ReadOnly or vice versa. The ReadWriteMode property cannot ...
  48. The database with ID '%{dbid/}' cannot be created with ReadWriteMode set to ReadOnly. A database can only be created in ReadWrite ...
  49. The database with name '%{DBName/}', ID '%{DBId/}' cannot be restored since it already exists on the server and is read-only. ...
  50. The database with name '%{DBName/}', ID '%{DBId/}' cannot be synchronized since it already exists on the target server and ...
  51. The database within this workbook was created by a newer version of PowerPivot (version: '%{compLevel/}') and cannot be opened. ...
  52. The database you have selected is not a report server database. Please select a SQL Server database that contains report ...
  53. The database {0} exists on the SQL Server. You must choose a different database or install Master Data Services into existing ...
  54. The database {0} exists on the SQL Server. You must choose a different database or install Reporting Services into existing ...
  55. The DataPoint {2} in the {0} {1}' has the name "{3}". DataValue names cannot be null and must be unique within the DataValues ...
  56. The DataPoints in the {0} {1}' has an invalid set of {2} items. {2} names must be unique within the {2} collection for the ...
  57. The dataset '{0}' has no spatial fields. Enter the name of a dataset with a field that is data type SqlGeography or SqlGeometry. ...
  58. The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data ...
  59. The dataset {1}' refers to the shared data set {3}', which is not published on the report server. The shared data set {3}' ...
  60. The dataset {1}' refers to the shared data source {3}', which is not published on the report server. The shared data source ...
  61. The datasource '%{datasource/}' requires an isolation level of SnapshotIsolation which is not supported by the database provider. ...
  62. The datasource in the current set of out-of-line bindings, '%{Datasource/}', contains an ImpersonationMode that cannot be ...
  63. The DataSource property of the specified DataGridView is not set to a BindingSource with a SupportsFiltering property value ...
  64. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  65. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  66. The DatastoreDocumentCondition element cannot be the root element of a document, it can only be used as the child of a Condition ...
  67. The DatastoreFlagCondition element cannot be the root element of a document, it can only be used as the child of a Condition ...
  68. The DatastoreProperties element cannot be the root element of a document, it can only be used as the child of an Action element. ...
  69. The DataType element of the binding for a mining structure column, whose content type is set to Date, must be also set to ...
  70. The datatype of the identity column of table '%1!s!' is tinyint. tinyint does not have enough numbers available for merge ...
  71. The DataType property for the {0} is {2}, but the default value Expression for "{1}" returns the data type {3}. The data ...
  72. The DataType property for the {0} is {2}, but the Expression for "{1}" returns the data type {3}. The DataType property for ...
  73. The DataType property for the {0} is {2}, but the {1} has the data type {3}. The DataType property for the Attribute must ...
  74. The DataTypeCompatibility property of ADO type connection manager "%1!s!" was set to 80 for backward compatibility reasons. ...
  75. The DataTypeCompatibility property of ADO type connection manager "{0}" was set to 80 for backward compatibility reasons. ...