UI Translation

SQL Server 2008

  1. The expression used for the parameter {1}' in the dataset {3}' refers to a field. Fields cannot be used in query parameter ...
  2. The expression used for the parameter {1}' in the dataset {3}' refers to a report item. Report items cannot be used in query ...
  3. The expression used for the parameter {1}' in the dataset {3}' uses the aggregate function Previous. Previous cannot be used ...
  4. The expression used for the parameter {1}' in the dataset {3}' uses the aggregate function RunningValue. RunningValue cannot ...
  5. The extended event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information ...
  6. The extended event engine has been disabled by startup options. Features that depend on extended events may fail to start. ...
  7. The extension, "%1!s!", was implicitly upgraded to "%2!s!". Add a mapping for this extension to the UpgradeMappings directory. ...
  8. The extension, "{0}", was implicitly upgraded to "{1}". Add a mapping for this extension to the UpgradeMappings directory. ...
  9. The external metadata collection is improperly used by this component. The component should use external metadata when appending ...
  10. The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher '%1!s!' did not alter any meta data at the ...
  11. The failover cluster group is already owned by the upgraded nodes of the SQL Server instance, so it is not possible to transfer ...
  12. The failover instance name could not be retrieved. The settings cannot be updated. Check whether the Active Node is accessible ...
  13. The fast load destination is not valid. To use fast load, a table or a view must be selected or an SQL statement of the form ...
  14. The feature state notification message received from the MSI has an invalid number of arguments. Each feature must include ...
  15. The field with the name {1}' in the dataset {3}' has both or neither of the following properties: DataField and Value. Fields ...
  16. The file "%1!s!" has been modified in the system catalog. The new path will be used the next time the database is started. ...
  17. The file "%1!s!" is ambiguous. The identity in the backup set does not match the file that is currently defined in the online ...
  18. The file "%1!s!" is missing. Roll forward stops at log sequence number %2!s!. The file is created at log sequence number ...
  19. The file "%1!s!" is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue. ...
  20. The file "%1!s!" is selected. At the time of backup it was known by the name "%2!s!". RESTORE will continue operating upon ...
  21. The file "%1!s!" was not fully restored by a database or file restore. The entire file must be successfully restored before ...
  22. The file "{0}" already exists at the destination. Do you want to overwrite the package at destination? Click Yes to overwrite ...
  23. The file %1!s! has been expanded to allow recovery to succeed. After recovery completes, you can increase the size of the ...
  24. The file '%1!s!' of restored database '%2!s!' is being left in the defunct state because the database is being upgraded from ...
  25. The file '%1!s!' of restored database '%2!s!' is being left in the defunct state because the database is using the simple ...
  26. The file '%1' is open in an editor with unsaved changes. Do you want to save your changes before invoking Open With on this ...
  27. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  28. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  29. The file '{0}' is not copied to the alternate snapshot location because the alternate snapshot location is configured to ...
  30. The file 2][3 is being held in use{ by the following process: Name: 4], Id: 5], Window Title: '[6]'}. Close that application ...
  31. The file cannot be opened for reading the metadata. If the file does not exist, and the component has already defined external ...
  32. The file header in '%1!s!' does not match the expected contents for file '%2!s!' of database '%3!s!'. The mismatch is possibly ...
  33. The file name contains invalid characters. Please use a different name. Invalid characters include the following: {0}. The ...
  34. The file name is not properly specified. Supply the path and name to the raw file either directly in the FileName property ...
  35. The file or filegroup "%1!s!" is not in a valid state for the "Recover Data Only" option to be used. Only secondary files ...
  36. The file path '{0}' contains invalid characters, is empty, or contains only white spaces, or contains a wildcard character. ...
  37. The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than ...
  38. The file specified in the For Each File enumerator is not valid. Check that the file specified in the For Each File enumerator ...
  39. The file {0} already exists. Do you want to overwrite it? Click Yes to overwrite the existing file. Click No to cancel this ...
  40. The file {0}' contains one or more custom report items (CRIs) that have unsupported features that might not render in the ...
  41. The file, "%1!s!", could not be opened for writing. The file could be read-only, or you do not have the correct permissions. ...
  42. The filegroup "%1!s!" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot ...
  43. The filegroup "%1!s!" is ambiguous. The identity in the backup set does not match the filegroup that is currently defined ...
  44. The filegroup "%1!s!" is selected. At the time of backup it was known by the name "%2!s!"'. RESTORE will continue operating ...
  45. The FILESTREAM column cannot be used with method %1!s! because the associated ROWGUIDCOL of the base table is nullable or ...
  46. The FILESTREAM configuration is not the same for each cluster node. FILESTREAM must be set to the same access level and share ...
  47. The FILESTREAM file system log record that has the LSN '%1!s!:%2!s!:%3!s!' is missing. Log folder '%4!s!' is corrupted. Restore ...
  48. The FILESTREAM filegroup '%1!s!' has no files assigned to it. FILESTREAM data cannot be populated on this filegroup until ...
  49. The FILESTREAM share can only be changed when FILESTREAM is enabled for streaming access. You should disable FILESTREAM streaming ...
  50. The Fill from Example tool extends examples in one partially filled column to all the rows of the table. This tool uses expert ...
  51. The filter contains an operator that is not supported for the content type of the operand column (at line %d{Line/}, column ...
  52. The Filter Expression for the {0} returns a set of values for each instance of the {1}. This expression must return a single ...
  53. The filter for {0} {1}' has an incorrect number of filter values for the operator. The operator {3}' requires exactly {4} ...
  54. The filtered index tuning option -fi is not supported when -fa is IV or with the -fx option. The -fi option is valid for ...
  55. The final feature state for package '{0}' has already been received via a notification. Reporting the final feature state ...
  56. The final value of the output parameter was null, and could not be sent to a 6.5 client expecting the parameter to be non-nullable. ...
  57. The first argument of the 'Rank' function, a tuple expression, should reference the same hierarchies as the second argument, ...
  58. The fixed length property was attempted to be set for column %1!Iu! which can not be of fixed length. InMemory Rowset creation ...
  59. The folder "{0}" cannot be moved to the target location. The destination folder "{1}" is a subfolder of the source folder ...
  60. The folders which are accessible through the network share is displayed. Select the folder location of the database files ...
  61. The following applications are using files that must be updated as part of this installation. To continue, close the applications ...
  62. The following applications are using files that need to be updated by this installation. Close these applications and click ...
  63. The following applications are using files that need to be updated by this setup. Close these applications and then click ...
  64. The following applications are using files that need to be updated by this setup. You can let Setup Wizard close them and ...
  65. The following columns cannot be mapped: {0} One or more columns do not have supported data types, or their data types do ...
  66. The following conflicts were detected during the download phase of message processing. These will be resolved during the ...
  67. The following credentials are used by the report server to connect to the report server database. Use the options below to ...
  68. The following cube attributes have been selected to be used by the mining structure and have their attribute hierarchy disabled: ...
  69. The following custom properties cannot be updated due to ambiguity when referencing input columns: {0} If the component does ...
  70. The following data type properties of column ' ' do not match those of ' '. Select a column with the same data type properties ...
  71. The following error occurred because the filter expression is not valid: '{0}' Correct the filter expression and try again. ...
  72. The following error occurred while a table was being created in a data source view: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  73. The following error occurred while a table was being dropped from a data source view: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  74. The following error occurred while the '%{pathfrom/}' file was being copied to the '%{pathto/}' file: %1[ %{External/}%]%[, ...
  75. The following exception occurred while an operation was being performed on a data source view: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
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)