UI Translation

SQL Server 2016

  1. The columns cannot be matched using the names. Try to map them manually by choosing appropriate ones from the list of available ...
  2. The columns of table {1} are mapped to AssociationSet {2}'s End {3} but the key columns of table {4} are not mapped to the ...
  3. The columns specified in the PATH function must be from the same table, have the same data type and that type must be Integer ...
  4. The combination of scheduled polling and incremental updates can only be specified when the storage mode is MOLAP. The current ...
  5. The combined size of the databases in the Availability Group is {0}. Seeding the replica in Microsoft Azure may take a long ...
  6. The command %1!s! failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name ...
  7. The command cannot be completed. No tables were detected in the active Excel workbook that are linked to PowerPivot tables. ...
  8. The command failed because Query Store is disabled on the server or database you are using. Contact customer support to get ...
  9. The command failed because the query store is not enabled for database (%1!s!). Make sure that the query store is enabled ...
  10. The command failed because the query store is not in read-write mode for database (%1!s!). Make sure that the query store ...
  11. The command is still associated with an open data reader. Changes cannot be made on this command and this command cannot ...
  12. The command line specified in the definition file is too long; the maximum length allowed is %1!u! characters. Use a user-defined ...
  13. The command line specified is too long. The maximum length allowed is %1!u! characters. Shorten the command line or use an ...
  14. The command specified for the dataset '{0}' is using an expression. Expressions are not supported in command text field when ...
  15. The command type '{1}' specified for the dataset '{0}' is not supported when rendering a report in Management Studio. The ...
  16. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  17. The commit mode for the replica '{0}' has already changed before failover. Verify the commit mode and re-run the Failover ...
  18. The commit transaction operation cannot be executed since it is attempting to modify the contents of the read only database ...
  19. The common criteria compliance enabled option enables the following: Residual Information Protection (RIP), the ability to ...
  20. The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated ...
  21. The Common Language Runtime (CLR) was loaded in an unsupported manner. This can occur if an extended stored procedure or ...
  22. The comparison flags for "%1!s!" must be zero because its type is not a string type. ComparisonFlags can only be non-zero ...
  23. The ComparisonFlags property cannot be set to a non-zero value for "%1!s!" because the "%2!s!" is not a source output. The ...
  24. The compatibility level of database '%{name/}' can only be upgraded by scripting the entire database (including child objects). ...
  25. The compatibility level of the new database does not support a management data warehouse. Select a different database, or ...
  26. The complex member '{0}' in type '{1}' and the complex member '{2}' in type '{3}' are incompatible because they have a different ...
  27. The COMPLEXITY_PENALTY parameter for the '%{modelname/}' model is not valid. COMPLEXITY_PENALTY must be greater than 0 and ...
  28. The component cannot use a connection manager that retains its connection in a transaction with fastload or bulk insert. ...
  29. The component could not be added to the Data Flow task. Verify that this component is properly installed. Component information: ...
  30. The component has detected potential metadata corruption during validation. {0} Click OK to continue to the advanced editor. ...
  31. The component has detected potential metadata corruption during validation. {0} Due to limitations of the Advanced Editor ...
  32. The component has detected potential metadata corruption during validation. {0} It may not be possible to recover to a valid ...
  33. The component has no available input columns and cannot be configured correctly. To correct the problem, connect an output ...
  34. The component is displaying no column information or is displaying old column information because an error occurred while ...
  35. The component is displaying no column information or is displaying old column information because the option, Work Offline, ...
  36. The component is displaying no column information or may be displaying old column information because the option, Work Offline, ...
  37. The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this ...
  38. The component is not in a valid state. The validation errors are: {0} Do you want the component to fix these errors automatically? ...
  39. The component locale ID has not been set. Flat file adapters need to have the locale ID on the flat file connection manager ...
  40. The component metadata for "%1!s!" could not be downgraded to the older version of the component. The PerformDowngrade method ...
  41. The component metadata for "%1!s!" could not be upgraded to the newer version of the component. The PerformUpgrade method ...
  42. The component reported the following warnings: {0} Choose OK if you want to continue with the operation. Choose Cancel if ...
  43. The component view ID is incorrect. The component view may be out of synchronization. Try releasing the component view and ...
  44. The component was not able to set the value, "{0}", from the data flow element, "{1}", to table element, "{2}", because of ...
  45. The CompoundCurve input is not valid because it does not have enough points. A CompoundCurve must have at least two points. ...
  46. The compressed size of the cabinet has just exceeded the SQL Replication's predefined limit of {0} bytes, retry the operation ...
  47. The COMPUTE clause generates totals that appear as additional summary columns at the end of the result set. However, this ...
  48. The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the max (varchar, ...
  49. The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the user-defined ...
  50. The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the xml column ...
  51. The computer cannot access the Internet. There might be delays in starting a .NET application like Management Studio. If ...
  52. The conceptual side property '{0}' has already been mapped to a storage property with type '{1}'. If the conceptual side ...
  53. The concurrent snapshot for publication '%1!s!' is not available because it has not been fully generated or the Log Reader ...
  54. The condition passed in to the FeatureResultPostExecutionListener trigger on action {0} did not report the failed feature ...
  55. The condition passed in to the FeatureResultPostExecutionListener trigger on action {0} uses a static method on the {1} type ...
  56. The condition passed in to the FeatureResultPostExecutionListener trigger on action {0} uses the {1} type which is not supported. ...
  57. The condition value specified for {0} is not compatible with the type returned by the storage provider. Column name: '{1}', ...
  58. The conditional expression "%1!s!" of the conditional operator has an invalid data type of "%2!s!". The conditional expression ...
  59. The conditional expression of the conditional operator has invalid data type. The conditional expression must be of type ...
  60. The conditional operation "%1!s!" failed with error code 2!8.8X!. There was an internal error or an out-of-memory error. ...
  61. The configuration and operation of each instance feature of a SQL Server instance is isolated from other SQL Server instances. ...
  62. The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL ...
  63. The configuration entry "%1!s!" had an incorrect format. This can occur because of a missing delimiter or formatting errors, ...
  64. The configuration entry "%1!s!" in the configuration file was not valid, or failed to configure the variable. The name indicates ...
  65. The configuration entry, "%1!s!", has an incorrect format because it does not begin with package delimiter. There was no ...
  66. The configuration entry, "%1!s!", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" ...
  67. The configuration environment variable was not found. The environment variable was: "%1!s!". This occurs when a package specifies ...
  68. The configuration file loaded, but is not valid. The file is not formatted correctly, may be missing an element, or may be ...
  69. The configuration of endpoint data encryption is incompatible between replicas and the endpoint connection will fail. The ...
  70. The configuration of endpoint data encryption is incompatible between replicas and the endpoint connection will fail. {0} ...
  71. The configuration of secondary database {0}].[{1} has been changed at the secondary server instance. The database is no longer ...
  72. The configuration of secondary database {0}].[{1} has been changed at the secondary server instance. The database is now ...
  73. The configuration parameter SharePointIntegrated is set to True but Share Point Object Model cannot be loaded. The error ...
  74. The configuration path could not be retrieved from the active node. Check whether you can reach the active node from the ...
  75. The configuration path on the passive node is different from the configuration path on the active node. The passive node's ...
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)