UI Translation

SQL Server 2008

  1. The following exception occurred while the managed IDataReader interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  2. The following exception occurred while the managed IDbCommand interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  3. The following exception occurred while the managed IDbConnection interface was being used: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  4. The following exception occurred while the Time Dimension Generator (Microsoft.AnalysisServices.TimeDimGenerator.dll) was ...
  5. The following existing dimensions were not added to the cube because the wizard could not determine how to use them in a ...
  6. The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives. ...
  7. The following information will be used to connect to an existing report server database. Verify this information is correct ...
  8. The following information will be used to create a new report server database. Verify this information is correct before ...
  9. The following member unique names specified in the attribute permission are no longer valid: {0} Do you wish to remove them? ...
  10. The following members are from a measure group that is not related to the currency dimension: {0} You can either go back ...
  11. The following mining model will be deleted from the mining structure: {0} The following mining structure column will be deleted ...
  12. The following mining structure column will be deleted from the mining structure: {0} Any related mining model columns will ...
  13. The following mining structure columns will be removed from the '{0}' nested table due to a mining structure key change: ...
  14. The following objects were not found in SQL Server. Please convert and synchronize them in order to proceed with the Test ...
  15. The following objects will be cleared (unprocessed) when the objects selected will be processed. Check the box if you want ...
  16. The following partitions or dimension attributes do not contain records, possibly because the filter is too restrictive: ...
  17. The following peers do not contain the peer information required to set up the topology: {0} The backup file from database ...
  18. The following products depend on ProductShortName]: 2 If you uninstall ProductShortName], dependent products might not function ...
  19. The following resources could not be configured during repair without additional user input. Review the warnings to understand ...
  20. The following Subscribers cannot replicate their data changes because they are not Registered Subscribers at the Publisher: ...
  21. The following system error occurred during a call to GetFileSize for file: '%{Note1/}'%1[: %{External/}%]%[, %{External/}%]. ...
  22. The following system error occurred from a call to GetOverlappedResult for Physical file: '%{PhysicalFile/}', Logical file: ...
  23. The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing ...
  24. The FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement ...
  25. The For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern, ...
  26. The FOR XML clause is invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. ...
  27. The FORCE_REGRESSOR parameter for the '%{modelname/}' model is not valid. The '%{strParamName/}' column must be an input ...
  28. The Forecast tool performs forecasting on a selected table. The forecasted values are added to the original table and highlighted. ...
  29. The FORECAST_METHOD parameter for the '%{modelname/}' model is not valid. FORECAST_METHOD should be one of the three values ...
  30. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it depends on the unpublished default constraint ...
  31. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the key constraint '{4}.{5}.{6}' ...
  32. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished key constraint ...
  33. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished table '{4}.{5}'. ...
  34. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because one of its referencing columns '{4}' is unpublished. ...
  35. The foreign key column {0} is used as an input or predictable column in the nested table {1}. This is highly discouraged. ...
  36. The Form View cannot be displayed because the MDX script has the following syntax error: '{0}' To correct this error, click ...
  37. The formal parameter "%1!s!" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. ...
  38. The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured ...
  39. The format used to define the new variable for Invoke-Sqlcmd cmdlet is invalid. Please use the "var=value" format for defining ...
  40. The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events ...
  41. The forwarded message number {0}:{1} on conversation {2}:{3} from service {4} to service {5} was dropped with the following ...
  42. The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions. ...
  43. The fractional part of the provided time value overflows the scale of the corresponding SQL Server parameter or column. Increase ...
  44. The FromClause properties of columns are not valid. This is frequently due to using the same table alias for different tables. ...
  45. The Full aggregation usage setting should be avoided in cases where an attribute contains a large number of members. If specified ...
  46. The full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) will be remounted to recover from a failure. Reason code: ...
  47. The full-text catalog health monitor reported a failure for full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!). ...
  48. The full-text catalog monitor reported catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) in %5!s! state. This is an informational ...
  49. The full-text filter component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current ...
  50. the full-text for , which in full-text indexing on table ' '. After this change, will no longer participate in the table's ...
  51. The full-text index cannot be created because filegroup '%1!s!' does not exist or the filegroup name is incorrectly specified. ...
  52. The full-text index on table '{0}.{1}' will not be scripted for article '{2}' because it references the unpublished unique ...
  53. The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to ...
  54. The full-text population on table '%1!s!' cannot be started because the full-text catalog is importing data from existing ...
  55. The full-text protocol handler component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not ...
  56. The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values ...
  57. The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a ...
  58. The full-text word-breaker component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the ...
  59. The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs ...
  60. The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning ...
  61. The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type ...
  62. The fulltext stoplist '%1!s!' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the ...
  63. The fulltext stoplist '%1!s!' does not exist or the current user does not have permission to perform this action. Verify ...
  64. The function "%1!s!" does not support the data type "%2!s!" for parameter number %3!d!. The type of the parameter could not ...
  65. The function "%1!s!" requires %2!d! parameter, not %3!d! parameters. The function name was recognized, but the number of ...
  66. The function "%1!s!" requires %2!d! parameters, not %3!d! parameter. The function name was recognized, but the number of ...
  67. The function "%1!s!" requires %2!d! parameters, not %3!d! parameters. The function name was recognized, but the number of ...
  68. The functionality you're trying to execute is disabled inside SQLCLR, if you still want to execute this functionality you ...
  69. The functions IsInNode or IsDescendant should be used only once and no OR operator should be used together at line %d{Line/}, ...
  70. The fuzzy lookup specified between input column "%1!s!" and reference column "%2!s!" is not valid because fuzzy joins are ...
  71. The Generate SQL Server Scripts Wizard allows you to generate scripts for databases and objects inside databases. This wizard ...
  72. The generated script file path '%1' has exceeded the length limit of %2!d! characters imposed by the Snapshot agent. Reducing ...
  73. The geometry index n ({0}) passed to STGeometryN is less than 1. The number must be greater than or equal to 1 and should ...
  74. The geometryType argument to InstanceOf ('{0}') is not valid. This argument must contain one of the following types: Geometry, ...
  75. The GetEnumerator method of the ForEach Enumerator has failed with error 1!8.8X! "%2!s!". This occurs when the ForEach Enumerator ...
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)