UI Translation

SQL Server 2012

  1. The Channel Bindings from this client do not match the established Transport Layer Security (TLS) Channel. The service might ...
  2. The character at which to start the search; if omitted, StartPosition = 1. The first character in WithinText is character ...
  3. The character length %1!Iu! specified for type "%2" for column %3!Iu! exceeded the maximum SQL Server allowed length of %4!d! ...
  4. The chart series {0} is missing and cannot be deserialized. You can use Chart.CallbackStateContent='All' to preserve all ...
  5. The check constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  6. The check for a Publisher needing a new identity range allocation failed on table %1!s!. This check occurs every time the ...
  7. The checkpoint file "%1!s!" is locked by another process. This may occur if another instance of this package is currently ...
  8. The checksum function used by the merge process to perform data validation on article '%1' returned an invalid checksum value. ...
  9. The CircularString input is not valid because it does not have enough points. A CircularString must have at least three points. ...
  10. The Claims to Windows Token service is used to extract a Windows user identity from a SharePoint claims token during PowerPivot ...
  11. The client '%1!s!' failed to register with controller '%2!s!' because the maximum number of clients has been exceeded based ...
  12. The client '{0}' is not a registered distributed replay client. Make sure that the SQL Server Distributed Replay Client services ...
  13. The client cannot connect to the server because the requested instance was not available. Use SQL Server Configuration Manager ...
  14. The client code page %1!u! does not have a corresponding SQL Server Collation. The Table-Valued Parameter could not be sent. ...
  15. The client components on this workstation must be upgraded before a connection can be established to this instance of Analysis ...
  16. The client computer ran out of disk space while generating the dispatch file, the result trace file or log files during the ...
  17. The client library requires a different version of the database schema ({0}). Install the required version of the database ...
  18. The client library requires a newer version of the database schema ({1}). The current database schema version is ({0}). Install ...
  19. The client service account cannot create the dispatch file in the client working directory. Confirm that the client service ...
  20. The client service account cannot create the result trace file in the client result directory. Confirm that this client service ...
  21. The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the ...
  22. The client was unable to join a session with SPID %1!s!. This error may have been caused by an earlier operation failing ...
  23. The client was unable to reuse a session with SPID %1!s!, which had been reset for connection pooling. The failure ID is ...
  24. The client's metadata is out of sync with the engine's metadata. The reference returned by the engine is unknown in the client: ...
  25. The CLR procedure/function/type being signed refers to an assembly that is not signed either by a strong name or an assembly. ...
  26. The CLR type referenced by column "%1!s!" of table variable "%2!s!" has been dropped during the execution of the batch. Run ...
  27. The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not ...
  28. The cluster disk '{0}' can not be owned by the node(s) {1} so it cannot be used as a cluster disk. To use this disk, add ...
  29. The cluster disk '{0}' cannot be selected because it is mounted on the following cluster resources: {1}. Choose the root ...
  30. The cluster disk '{0}' could not be brought online. The disk must be online in order for the SQL Server failover cluster ...
  31. The cluster disk '{0}' is not owned by the local node so it cannot be used as a cluster disk. To use this disk, move it to ...
  32. The cluster disk device name '{0}' is not valid. Supported devices names include drive letters, OS object name, and volume ...
  33. The cluster disk resource '{0}' is not online. Some operations may fail if the disk cannot be brought online for disk operations. ...
  34. The cluster either has not been verified or there are errors or failures in the verification report. Refer to KB953748 or ...
  35. The cluster group '{0}' contains resource '{1}' of type '{2}' that are not permitted in a SQL cluster group. Ensure the cluster ...
  36. The cluster group cannot be determined for the instance name '{0}'. This indicates there is a problem with the product registry ...
  37. The cluster group name cannot be null or empty and cannot contain ' or \. To continue, specify a valid group name and retry, ...
  38. The cluster group name for group '{0}' could not be determined. Error: {1}. Ensure that the name you provided is correct, ...
  39. The cluster group type for group '{0}' could not be determined. Error: {1}. Ensure that the group name you provided is correct, ...
  40. The Cluster Group {0} is active on the node where SQL Server Setup is running. To continue, the group must be either be owned ...
  41. The Cluster Group {0} is not owned by the node where SQL Server Setup is running. To continue, run Setup again on the node ...
  42. The cluster network '{0}' does not have a bound IPv4 address which indicates IPv4 is not supported for that network. Bind ...
  43. The cluster network '{0}' does not have a bound IPv6 address which indicates IPv6 is not supported for that network. Bind ...
  44. The cluster network name '{0}' could not be taken offline. To continue, take the network name offline before you delete it. ...
  45. The cluster node name '{0}' is invalid. The specified computer is not a cluster node in this SQL Server failover cluster. ...
  46. The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available. ...
  47. The cluster operation cannot be completed because no clustered feature is available. The failover cluster name cannot be ...
  48. The cluster resource '{0}' could not be brought online due to an error bringing the dependency resource '{1}' online. Refer ...
  49. The cluster resource with type '{0}' and property '{1}' = '{2}'could not be found on the cluster. Please check if it exists. ...
  50. The Cluster Service function call '%1!s!' failed with error code '%2!s!' while verifying the file path. Verify that your ...
  51. The clustered index '%1!s!' on table '%2!s!' cannot be disabled because the table has change tracking enabled. Disable change ...
  52. The clustered index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  53. The clustered index on materialized view '%1!s!' may not contain nullable columns if it is to be published using the transaction-based ...
  54. The clustering method the algorithm uses can be either: Scalable EM (1), Non-scalable EM (2), Scalable K-means (3), or Non-scalable ...
  55. The ClusterProbability function returns the probability of the input case belonging to the specified (or most likely) cluster. ...
  56. The code page %1!d! specified on column "%2!s!" (%3!d!) is not supported. You must first convert this column to DT_WSTR which ...
  57. The code page %1!d! specified on output column "%2!s!" (%3!d!) is not valid. Select a different code page for output column ...
  58. The code pages do not match in a binary operation. The code page of the left operand does not match the code page of the ...
  59. The code pages do not match in a conditional operation. The code page of the left operand does not match the code page of ...
  60. The code pages for operands of binary operator "%1!s!" for type "%2!s!" must match. Currently, the code page of the left ...
  61. The code pages must match for operands of conditional operation "%1!s!" for type %2!s!. The code page of the left operand ...
  62. The code pages of the DT_STR source column "%1!s!" and the DT_STR dest column "%2!s!" do not match. This may cause unexpected ...
  63. The COLLATE CATALOG_DEFAULT clause cannot be used in a constraint, computed column, index filter expression, or any schema-bound ...
  64. The collation you specified does not support the supplementary characters flag. To proceed, specify a Windows collation version ...
  65. The column "%1!s!" (%2!d!) cannot be matched to any input file column. The output column name or input column name cannot ...
  66. The column "%1!s!" at index %2!d! in the flat file connection manager was not found at index %3!d! in the column collection ...
  67. The column "%1!s!" in the pre-built index "%2!s!" was not found in the reference table/query. This happens if the schema/query ...
  68. The column '%1!s!' cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a ...
  69. The column '%1!s!' cannot be added to table '%2!s!' as it is a FileTable. Adding columns to the fixed schema of a FileTable ...
  70. The column '%1!s!' does not have a valid data type for the ORDER hint specified for data source '%2!s!'. The text, ntext, ...
  71. The column '%1!s!' in table '%2!s!' is involved in a foreign key relationship with a column in table '%3!s!', but this column ...
  72. The column '%1!s!' in the table '%2!s!' cannot be referenced in a CHECK constraint or computed column definition because ...
  73. The column '%1!s!' specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function ...
  74. The column '%1!s!' that was returned from the nodes() method cannot be used directly. It can only be used with one of the ...
  75. The column '%{table/}[%{column/}]' either doesn't exist or doesn't have a relationship to any table available in the current ...
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)