SQL Server 2012

  1. The data mining relationship cannot be defined because the {0} case dimension is absent in this cube and needs to be added. ...
  2. The Data Mining Training transformation requires at least one input. Connect an output from a source or another transformation ...
  3. The data processing extension used for this data source is not available. It has either been uninstalled, or it is not configured ...
  4. The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured ...
  5. The data refresh job failed to update the PowerPivot workbook because another user modified the file while data refresh was ...
  6. The data source '{0}' uses a custom data processing extension which does not implement IDbConnectionExtension. Therefore, ...
  7. The data source '{0}' uses a managed data provider which does not implement IDbConnectionExtension. Only Windows Integrated ...
  8. The data source is configured to prompt for credentials but no prompt text has been entered. Enter prompt text for the data ...
  9. The data source may might not be accessible from the location where the report was saved. The report was saved to "{0}". ...
  10. The data source table with id '{0}' was not found while adding to the repository. Check whether the table is accessible by ...
  11. The data source view does not contain a definition for the '%{table/}' table or view. The Source property may not have been ...
  12. The data source view for the cube does not contain some tables, named calculations, primary keys, or relationships used by ...
  13. The data source {1}' has both or neither of the following: DataSourceReference and ConnectionProperties. DataSource must ...
  14. The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, ...
  15. The data tap '%1!s!' does not exist, or you do not have sufficient permissions to remove it. Provide a valid data tap ID. ...
  16. The data type "%1!s!" cannot be compared. Comparison of that data type is not supported, so it cannot be sorted or used as ...
  17. The data type "%1!s!" cannot be used with binary operator "%2!s!". The type of one or both of the operands is not supported ...
  18. The data type "%1!s!" cannot be used with unary operator "%2!s!". This operand type is not supported for the operation. To ...
  19. The data type "%1!s!" found on column "%2!s!" is not supported for the %3!s!. This column will be converted to DT_NTEXT. ...
  20. The data type "%1!s!" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), ...
  21. The data type %1!s! cannot be used as an operand to the UNION, INTERSECT or EXCEPT operators because it is not comparable. ...
  22. The data type %1!s! does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings. ...
  23. The data type %1!s! is invalid for the %2!s! function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. ...
  24. The data type conversion file, {0}, cannot be located. Therefore, the wizard cannot provide information about the conversion ...
  25. The data type for "%1!s!" is DT_IMAGE, which is not supported. Use DT_TEXT or DT_NTEXT instead and convert the data from, ...
  26. The data type for "%1!s!" is DT_NTEXT, which is not supported with ANSI files. Use DT_TEXT instead and convert the data to ...
  27. The data type for "%1!s!" is DT_TEXT, which is not supported with Unicode files. Use DT_NTEXT instead and convert the data ...
  28. The data type is about to be changed for the column. This will affect how the data is stored and might impact data precision ...
  29. The data type is about to be changed for the column. This will affect how the PowerPivot data is stored and might impact ...
  30. The data type mapping for %1!s! does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings. ...
  31. The data type of a foreign key binding (ordinal=%{iOrdinal/}) for the '%{tablecolumn/}' nested table does not match the data ...
  32. The data type of the %{structure/}.%{dmscolumn/} mining structure column must be numeric since it has a continuous content ...
  33. The data type of the '%{measure/}' measure must be the same as its source data type. This is because the aggregate function ...
  34. The data type of the parameter "{0}" is {1}. However, one or more of the values provided for the parameter cannot be converted ...
  35. The data type of the parameter "{0}" is {1}. However, the value provided for the parameter cannot be converted to this type. ...
  36. The data type of the {0} named calculation will be changed, and the following associated relationships will be removed:'{1}' ...
  37. The data type specified for the '%{column/}' column of the '%{structure/}' OLAP mining structure is not compatible with its ...
  38. The data types "%1!s!" and "%2!s!" are incompatible for binary operator "%3!s!". The operand types could not be implicitly ...
  39. The data types "%1!s!" and "%2!s!" are incompatible for the conditional operator. The operand types cannot be implicitly ...
  40. The data types of the operands of the conditional operator were incompatible. The operand types could not be implicitly cast ...
  41. The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver ...
  42. The data-tier application cannot be upgraded because the database associated with the data-tier application is not available. ...
  43. The data-tier application was deleted from the instance. Refresh the Object Explorer pane before selecting a data-tier application. ...
  44. The database "%1!s!" does not exist. RESTORE can only create a database when restoring either a full backup or a file backup ...
  45. The database "%1!s!" is already configured for database mirroring on the remote server. Drop database mirroring on the remote ...
  46. The database "%1!s!" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire ...
  47. The database '%1!s!' at the redirected publisher '%2!s!' for original publisher '%3!s!' and database '%4!s!' belongs to a ...
  48. The database '%1!s!' at the redirected publisher '%2!s!' for original publisher '%3!s!' and database '%4!s!' is either not ...
  49. The database '%1!s!' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' ...
  50. The database '%1!s!' cannot be opened because it is version %2!s!. This server supports version %3!s! and earlier. A downgrade ...
  51. The database '%1!s!' cannot be removed from availability group '%2!s!'. This database does not belong to the availability ...
  52. The database '%1!s!' could not be created or altered to a contained database, because the check constraint '%2!s!' on table ...
  53. The database '%1!s!' could not be created or altered to a contained database, because the computed column '%2!s!' on %3!s! ...
  54. The database '%1!s!' could not be created or altered to a contained database, because the schema bound %2!s! '%3!s!' depends ...
  55. The database '%1!s!' does not exist or does not support FILESTREAM. Supply a valid database name. To see available databases, ...
  56. The database '%1!s!' does not exist or the database format is not valid. Provide a valid semantic language statistics database ...
  57. The database '%1!s!' is a readable secondary database in an availability group and cannot be enabled for FILESTREAM non-transacted ...
  58. The database '%1!s!' is currently joined to an availability group. Before you can drop the database, you need to remove it ...
  59. The database '%1!s!' is enabled for database mirroring. Database mirroring must be removed before you drop the database. ...
  60. The database '%1!s!' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the ...
  61. The database '{0}' already exists on the target instance of SQL Server. Specify a database name that does not already exist. ...
  62. The database '{0}' does not exist or is not available on the server '{1}'. Verify spelling of the database name and make ...
  63. The database , '%{Database/}', contains no Impersonation mode or an ImpersonationMode that is not supported for processing ...
  64. The database can not be brought online because file '%1!s!' is currently restored to LSN %2!s! but must be restored to LSN ...
  65. The database can not be created or altered as its definition contains circular dependency between regular and linked cubes. ...
  66. The database cannot be attached because an error occurred while loading the detach log from the file '%1'. One possible reason ...
  67. The database cannot be attached because an error occurred while loading the detach log from the file '%{db_detach_log/}'. ...
  68. The database cannot be attached because an error occurred while loading the detach log from the file '%{filename/}'. One ...
  69. The database cannot be attached because an error occurred while loading the detach log from the file '%{strRef/}'. One possible ...
  70. The database cannot be attached because it was detached from a server with ConnStringEncryptionEnabled=%d{BLSet/} and the ...
  71. The database cannot be attached because it was detached from a server with EnableCompression=%d{BLSet/} and the current server ...
  72. The database cannot be attached because it was detached from a server with EnableXMLMetadata=%d{BLSet/} and the current server ...
  73. The database cannot be attached because the detach log is corrupted. An error occurred when locating or processing the node ...
  74. The database configuration requires a newer version of the client library ({1}). The current library is ({0}). Install the ...
  75. The database connections has been changed from the original project settings. Your metabase is different from underlying ...