UI Translation

SQL Server 2008 R2

  1. /Cons[oleLog DispOpts];[{E | I};List DispOpts = any one or more of N, C, O, S, G, X, M, or T. List = {EventName | SrcName ...
  2. A %1!s! value was specified more than one time in the range list for an ALTER SERVER CONFIGURATION SET PROCESS AFFINITY statement. ...
  3. A .NET Framework error occurred during execution of user defined routine or aggregate '%1!s!': %2!s!. User transaction, if ...
  4. A bar chart displays data horizontally. It is popular for categorical information, because the categories can be displayed ...
  5. A blob store for storing a new blob could not be determined. This is because the blob store was not specified and no defaults ...
  6. A boolean that indicates whether the client application should provide a drillthrough link to the containing entity for this ...
  7. A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%1!s!:%2!s!:%3!s!}, ...
  8. A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query ...
  9. A calculation condition can optionally be used to further restrict the subcube by testing each cell with a logical MDX expression. ...
  10. A calculation subcube defines the subset of cube data that is computed using the calculation formula. For each dimension, ...
  11. A call to the ProcessInput method for input %1!d! on %2!s! unexpectedly kept a reference to the buffer it was passed. The ...
  12. A case that is not valid has been passed to the GetLag() function that is used with the '%{modelname/}' mining model. A time ...
  13. A change has occurred to the report manager identity. Reset the identity using the reporting services configuration tool. ...
  14. A change has occurred to the report server web service identity. Reset the identity using the reporting services configuration ...
  15. A change has occurred to the report server Windows service identity. Reset the identity using the reporting services configuration ...
  16. A change in security context was detected. Only the user that created the SqlRemoteBlobContext object can perform blob operations. ...
  17. A character could not be read from the file stream using the provided code page. The reason for this could be that a column ...
  18. A chart column in the chart {1}' has the name {3}'. Chart column names must be greater than 0 and less than or equal to {4} ...
  19. A client has disconnected from the Report Server Web service application domain {0}. No corrective action is required. An ...
  20. A cluster named, {0}, already exists. If you use this name, a new cluster will be created with the same name but a different ...
  21. A clustered instance of SQL Server could not be found to upgrade. Possible reasons are that the wrong instance name was specified, ...
  22. A collection of expressions. The evaluation result of each expression is assigned to a property and replaces the value of ...
  23. A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and ...
  24. A column chart displays a series as a set of vertical bars grouped by category. Column charts are useful for illustrating ...
  25. A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. ...
  26. A column used in filter clause '%1!s!' either does not exist in the table '%2!s!' or cannot be excluded from the current ...
  27. A command line argument was expected but not found. All command line arguments will be ignored. Please run 'profiler.exe ...
  28. A command to refresh a table '%{name/}' has failed because the command did not specify the correct number of columns in the ...
  29. A complete consistency check could not be performed. A previously started garbage collection (Reference Scan) operation is ...
  30. A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the ...
  31. A conditional expression with result types '{0}' and '{1}' is not supported and implicit conversion does not exist. Explicit ...
  32. A config item cannot be changed after it is constructed initially. An attempt was made to change the config item with key ...
  33. A configuration item with key is in the configuration item list. This configuration key cannot be used in this operation. ...
  34. A configuration item with key is not in the configuration item list. This configuration key is required for this operation. ...
  35. A configuration operation could not be performed on key because this key does not exist in the current collection. Check ...
  36. A conflict of type '%1!s!' was detected at peer %2!s! between peer %3!s! (incoming), transaction id %4!s! and peer %5!s! ...
  37. A connection cannot be reestablished because the connection properties were either lost when the connection was terminated ...
  38. A connection could not be made to the data source with the DataSourceID of '%{datasourceid/}', Name of '%{datasourcename/}'. ...
  39. A connection manager was automatically assigned to this data source. To assign a different connection manager, use the Advanced ...
  40. A connection time-out had occurred while connecting to the FTP site '%1'. This may be due to the fact that Internet Explorer ...
  41. A connection to Analysis Services is required to perform the {0} task. {1}Click the 'No Connection' button on the Data Mining ...
  42. A connection to Analysis Services is required to perform this task. Click the 'No Connection' button on the Analyze ribbon ...
  43. A connection to the report server database cannot be established. Verify that the SQL Server database is accessible on the ...
  44. A connection to the report server database cannot be established. Verify that the SQL Server database is accessible on the ...
  45. A CONTAINS or FREETEXT predicate can only operate on one table or indexed view. Qualify the use of with a table or indexed ...
  46. A conversation priority already exists in the database with either the name '%1!s!' or the properties %2!s!='%3!s!', %4!s!='%5!s!', ...
  47. A corrupted message has been received. A required variable data field is not present: %1!s!. This occurred in the message ...
  48. A corrupted message has been received. A sequence number is larger than allowed. This occurred in the message with Conversation ...
  49. A corrupted message has been received. A string variable data field is not a valid UNICODE string: %1!s!. This occurred in ...
  50. A corrupted message has been received. A UNICODE string is greater than the maximum allowed size of %1!s! bytes. This occurred ...
  51. A corrupted message has been received. A UNICODE string is not two byte aligned within the message. This occurred in the ...
  52. A corrupted message has been received. An unsequenced message had a non-zero sequence number. This occurred in the message ...
  53. A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID '%1!s!', ...
  54. A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. ...
  55. A corrupted message has been received. The binary header size of %1!s! is expected, however the header size received was ...
  56. A corrupted message has been received. The certificate issuer name size is %1!s!, however it must be no greater than %2!s! ...
  57. A corrupted message has been received. The certificate serial number size is %1!s!, however it must be no greater than %2!s! ...
  58. A corrupted message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ...
  59. A corrupted message has been received. The destination certificate issuer name size is %1!s!, however it must be no greater ...
  60. A corrupted message has been received. The destination certificate serial number is missing. This occurred in the message ...
  61. A corrupted message has been received. The destination certificate serial number size is %1!s!, however it must be no greater ...
  62. A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. ...
  63. A corrupted message has been received. The encrypted session key size is %1!s!, however it must be %2!s! bytes. This occurred ...
  64. A corrupted message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This ...
  65. A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message ...
  66. A corrupted message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. ...
  67. A corrupted message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred ...
  68. A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with ...
  69. A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. ...
  70. A corrupted message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ...
  71. A corrupted message has been received. The key exchange key size is %1!s!, however it must be between %2!s! and %3!s! bytes. ...
  72. A corrupted message has been received. The maximum number of private variable data elements (%1!s!) has been exceeded. Private ...
  73. A corrupted message has been received. The maximum number of public variable data elements (%1!s!) has been exceeded. Public ...
  74. A corrupted message has been received. The message body is not properly padded for encryption. This occurred in the message ...
  75. A corrupted message has been received. The message type is missing for this message. This occurred in the message with Conversation ...
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)