UI Translation

SQL Server 2008

  1. The Data Flow task failed to create a buffer to call PrimeOutput for output "%3!s!" (%4!d!) on component "%1!s!" (%2!d!). ...
  2. The Data Flow task failed to create a required thread and cannot begin running. The usually occurs when there is an out-of-memory ...
  3. The Data Flow task failed to initialize a required thread and cannot begin execution. The thread previously reported a specific ...
  4. The data in row {0} was not committed. Error Source: {1}. Error Message: {2} Correct the errors and retry or press ESC to ...
  5. The data in the column '{0}' does not have the required content type. In a mining structure that has a Key Time column, any ...
  6. The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset '%1!s!'. The data in the data ...
  7. The Data Mining Extensions (DMX) OPENROWSET statement supports ad hoc queries using external providers. Enable ad hoc data ...
  8. The Data Mining Extensions (DMX) OPENROWSET statement supports ad hoc queries using external providers. Enable ad hoc data ...
  9. The data mining relationship cannot be defined because the designer failed to identify the source dimension for mining model. ...
  10. The data mining relationship cannot be defined because the {0} case dimension is absent in this cube and needs to be added. ...
  11. The Data Mining Training transformation requires at least one input. Connect an output from a source or another transformation ...
  12. The data processing extension used for this data source is not available. It has either been uninstalled, or it is not configured ...
  13. The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured ...
  14. The data source '{0}' uses a custom data processing extension which does not implement IDbConnectionExtension. Therefore, ...
  15. The data source '{0}' uses a managed data provider which does not implement IDbConnectionExtension. Only Windows Integrated ...
  16. The data source may might not be accessible from the location where the report was saved. The report was saved to "{0}". ...
  17. The data source view does not contain a definition for the '%{table/}' table or view. The Source property may not have been ...
  18. The data source view for the cube does not contain some tables, named calculations, primary keys, or relationships used by ...
  19. The data source {1}' has both or neither of the following: DataSourceReference and ConnectionProperties. DataSource must ...
  20. The data type "%1!s!" cannot be compared. Comparison of that data type is not supported, so it cannot be sorted or used as ...
  21. 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 ...
  22. The data type "%1!s!" cannot be used with unary operator "%2!s!". This operand type is not supported for the operation. To ...
  23. 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. ...
  24. The data type "%1!s!" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), ...
  25. The data type %1!s! does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings. ...
  26. The data type %1!s! is invalid for the %2!s! function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. ...
  27. The data type conversion file, {0}, cannot be located. Therefore, the wizard cannot provide information about the conversion ...
  28. 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, ...
  29. 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 ...
  30. The data type for "%1!s!" is DT_TEXT, which is not supported with Unicode files. Use DT_NTEXT instead and convert the data ...
  31. The data type mapping for %1!s! does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings. ...
  32. The data type of a foreign key binding (ordinal=%{iOrdinal/}) for the '%{tablecolumn/}' nested table does not match the data ...
  33. The data type of the %{structure/}.%{dmscolumn/} mining structure column must be numeric since it has a continuous content ...
  34. The data type of the '%{measure/}' measure must be the same as its source data type. This is because the aggregate function ...
  35. The data type of the parameter "{0}" is {1}. However, one or more of the values provided for the parameter cannot be converted ...
  36. The data type of the parameter "{0}" is {1}. However, the value provided for the parameter cannot be converted to this type. ...
  37. The data type of the {0} named calculation will be changed, and the following associated relationships will be removed:'{1}' ...
  38. The data type specified for the '%{column/}' column of the '%{structure/}' OLAP mining structure is not compatible with its ...
  39. The data types "%1!s!" and "%2!s!" are incompatible for binary operator "%3!s!". The operand types could not be implicitly ...
  40. The data types "%1!s!" and "%2!s!" are incompatible for the conditional operator. The operand types cannot be implicitly ...
  41. The data types of the operands of the conditional operator were incompatible. The operand types could not be implicitly cast ...
  42. The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver ...
  43. The data viewer displays data flowing through a path during execution and can be configured to display data in numerous formats. ...
  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!' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' ...
  48. The database '%1!s!' cannot be opened because it is version %2!s!. This server supports version %3!s! and earlier. A downgrade ...
  49. The database '%1!s!' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the ...
  50. The database '{0}' does not exist or is not available on the server '{1}'. Verify spelling of the database name and make ...
  51. The database , '%{Database/}', contains no Impersonation mode or an ImpersonationMode that is not supported for processing ...
  52. The database can not be brought online because file '%1!s!' is currently restored to LSN %2!s! but must be restored to LSN ...
  53. The database can not be created or altered as its definition contains circular dependency between regular and linked cubes. ...
  54. The database cannot be attached because an error occurred while loading the detach log from the file '%1'. One possible reason ...
  55. The database cannot be attached because an error occurred while loading the detach log from the file '%{db_detach_log/}'. ...
  56. The database cannot be attached because an error occurred while loading the detach log from the file '%{filename/}'. One ...
  57. The database cannot be attached because an error occurred while loading the detach log from the file '%{strRef/}'. One possible ...
  58. The database cannot be attached because it was detached from a server with ConnStringEncryptionEnabled=%d{BLSet/} and the ...
  59. The database cannot be attached because it was detached from a server with EnableCompression=%d{BLSet/} and the current server ...
  60. The database cannot be attached because it was detached from a server with EnableXMLMetadata=%d{BLSet/} and the current server ...
  61. The database cannot be attached because the detach log is corrupted. An error occurred when locating or processing the node ...
  62. The database configuration requires a newer version of the client library ({1}). The current library is ({0}). Install the ...
  63. The database connections has been changed from the original project settings. Your metabase is different from underlying ...
  64. The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not ...
  65. The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. ...
  66. The Database Engine received a floating point exception from the operating system while processing a user request. Try the ...
  67. The Database Engine service could not resolve the specified file location. Either the location does not exist, or the current ...
  68. The Database Engine service could not resolve the specified folder location. Either the location does not exist, or the current ...
  69. The database folder '%{detach_log_location/}' does not exist, is too long, or contains characters that are not valid or are ...
  70. The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY ...
  71. 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 ...
  72. The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach ...
  73. The database is not valid due to the following errors: {0} Aggregation can only be designed for a valid database. Please ...
  74. The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the ...
  75. The database maintenance plan {0} contains log shipping settings. Those settings were not migrated to the new maintenance ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)