UI Translation

SQL Server 2012

  1. The following existing dimensions were not added to the cube because the wizard could not determine how to use them in a ...
  2. The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives. ...
  3. The following friendly names are not valid: {0}. A friendly name must be less than 100 characters, must not be a reserved ...
  4. The following import settings will be used to create a new Integration Services project. Click Import to begin importing ...
  5. The following information will be used to change credentials. Verify that this information is correct before you continue. ...
  6. The following information will be used to connect to an existing report server database. Verify this information is correct ...
  7. The following information will be used to create a new Master Data Services database. Verify that 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 information will be used to create the Master Data Services database. Verify that this information is correct ...
  10. The following member unique names specified in the attribute permission are no longer valid: {0} Do you wish to remove them? ...
  11. The following members are from a measure group that is not related to the currency dimension: {0} You can either go back ...
  12. The following mining model will be deleted from the mining structure: {0} The following mining structure column will be deleted ...
  13. The following mining structure column will be deleted from the mining structure: {0} Any related mining model columns will ...
  14. The following mining structure columns will be removed from the '{0}' nested table due to a mining structure key change: ...
  15. The following objects were not found in SQL Server. Please convert and synchronize them in order to proceed with the Test ...
  16. The following objects will be cleared (unprocessed) when the objects selected will be processed. Check the box if you want ...
  17. The following partitions or dimension attributes do not contain records, possibly because the filter is too restrictive: ...
  18. The following peers do not contain the peer information required to set up the topology: {0} The backup file from database ...
  19. The following products depend on ProductShortName]: 2 If you uninstall ProductShortName], dependent products might not function ...
  20. The following resources could not be configured during repair without additional user input. Review the warnings to understand ...
  21. The following services and applications are using files that Setup needs to complete the installation. To avoid a computer ...
  22. The following Subscribers cannot replicate their data changes because they are not Registered Subscribers at the Publisher: ...
  23. The following system error occurred during a call to GetFileSize for file: '%{Note1/}'%1[: %{External/}%]%[, %{External/}%]. ...
  24. The following system error occurred from a call to GetOverlappedResult for Physical file: '%{PhysicalFile/}', Logical file: ...
  25. The following Transact-SQL error occurred while attempting to execute a statement against the PowerPivot service application ...
  26. The following users or groups are invalid because they are not from the computer where the virtual directory is being created: ...
  27. The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing ...
  28. The For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern, ...
  29. The FOR XML clause is invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. ...
  30. The FORCESEEK hint cannot be used with index 0. Correct the index provided to the FORCESEEK hint and resubmit the query. ...
  31. The FORCE_REGRESSOR parameter for the '%{modelname/}' model is not valid. The '%{strParamName/}' column must be an input ...
  32. The Forecast tool performs forecasting on a selected table. The forecasted values are added to the original table and highlighted. ...
  33. The FORECAST_METHOD parameter for the '%{modelname/}' model is not valid. FORECAST_METHOD should be one of the three values ...
  34. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it depends on the unpublished default constraint ...
  35. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the key constraint '{4}.{5}.{6}' ...
  36. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished key constraint ...
  37. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished table '{4}.{5}'. ...
  38. The foreign key '{0}.{1}.{2}' will not be scripted for article '{3}' because one of its referencing columns '{4}' is unpublished. ...
  39. The foreign key column {0} is used as an input or predictable column in the nested table {1}. This is highly discouraged. ...
  40. The Form View cannot be displayed because the MDX script has the following syntax error: '{0}' To correct this error, click ...
  41. The formal parameter "%1!s!" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. ...
  42. The format for the date filter is incorrect. Please use a valid SQL Server date or datetime format. For example, valid formats ...
  43. The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured ...
  44. The format of supplied parameter sid is invalid. The sid might be incorrect or the sid might describe the wrong type of user. ...
  45. The format used to define the new variable for Invoke-Sqlcmd cmdlet is invalid. Please use the 'var=value' format for defining ...
  46. The formatting string. For example, C2 formats numbers as currency with 2 decimal places and N0 formats numbers with no decimal ...
  47. The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events ...
  48. The forwarded message number {0}:{1} on conversation {2}:{3} from service {4} to service {5} was dropped with the following ...
  49. The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions. ...
  50. The fractional part of the provided time value overflows the scale of the corresponding SQL Server parameter or column. Increase ...
  51. The friendly name, "{0}", is not valid. A friendly name must be less than 100 characters, must not be a reserved keyword, ...
  52. The Full aggregation usage setting should be avoided in cases where an attribute contains a large number of members. If specified ...
  53. The full path length of the LocalDB instance folder is longer than MAX_PATH. The instance must be stored in folder: %LOC ...
  54. The full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) will be remounted to recover from a failure. Reason code: ...
  55. The full-text catalog health monitor reported a failure for full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!). ...
  56. 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 ...
  57. The full-text filter component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current ...
  58. The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary. ...
  59. the full-text for , which in full-text indexing on table ' '. After this change, will no longer participate in the table's ...
  60. The full-text index cannot be created because filegroup '%1!s!' does not exist or the filegroup name is incorrectly specified. ...
  61. The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured ...
  62. The full-text index on table '{0}.{1}' will not be scripted for article '{2}' because it references the unpublished unique ...
  63. The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to ...
  64. The full-text population on table '%1!s!' cannot be started because the full-text catalog is importing data from existing ...
  65. The full-text protocol handler component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not ...
  66. The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values ...
  67. The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a ...
  68. The Full-Text Upgrade server property controls whether full-text indexes are imported, rebuilt, or reset for the restored ...
  69. The full-text word-breaker component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the ...
  70. The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs ...
  71. The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning ...
  72. The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type ...
  73. The fulltext stoplist '%1!s!' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the ...
  74. The fulltext stoplist '%1!s!' does not exist or the current user does not have permission to perform this action. Verify ...
  75. The function "%1!s!" does not support the data type "%2!s!" for parameter number %3!d!. The type of the parameter could not ...
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)