UI Translation

SQL Server 2008 R2

  1. The lengths of parameter names, types, and descriptions arrays are not equal. The lengths must be equal. This occurs when ...
  2. The level number specified for function fn_fulltext_compindex is not valid. Valid level numbers start from 0 and must be ...
  3. The level of the index. Level 0 is the leaf (or data) level of the index. Level number increases moving up the tree toward ...
  4. The level with ID of '%{levelid/}', Name of '%{levelname/}' referenced by the '%{cubehierarchy/}' cube hierarchy does not ...
  5. The license for the installation of SQL Server on '{0}' permits the server to use only itself as a Distributor. Refer to ...
  6. The license for this installation of SQL Server does not permit the creation of transactional publications. Refer to your ...
  7. The lineage ID of the output column that will receive the value from this input column. Or -1 if column's value is not used ...
  8. The lineage identifier of an input column that contains a PivotedValue or the value -1. The value -1 indicates the column ...
  9. The linearRing input is not valid because there are not enough points in the input. A linearRing must have at least 4 points, ...
  10. The LineString input is not valid because it does not have enough distinct points. A LineString must have at least two distinct ...
  11. The Linguistics property is specified for the {0}, but the Name property is omitted. Linguistics cannot be specified for ...
  12. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because it contains MG dimension ...
  13. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because its source object is not ...
  14. The list below shows which objects will be affected by the processing task. To process an object, select its check box. Selected ...
  15. The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %1!s! pages were ...
  16. The LoadFromSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  17. The local computer is an owner of a cluster group that contains the SQL Server service, Analysis Services service or a generic ...
  18. The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server ...
  19. The local computer is the only node left in the failover cluster that has not been upgraded, or it is a single-node failover ...
  20. The local connection is not available. This typically occurs because the AdomdServer object model is not being used within ...
  21. The local data source '{0}' contains a connection string that is an expression and cannot be converted to a shared data source. ...
  22. The local node of the failover cluster has already been upgraded, and no other nodes have been upgraded. It is not possible ...
  23. The local service account is different from the active node. Use the SQL Configuration Manager to change the service account ...
  24. The location for temporary storage of buffer data. You can specify multiple directories by using semicolons to delimit the ...
  25. The location for temporary storage of columns that contain binary large object (BLOB) data. You can specify multiple directories ...
  26. The location of the gauge image inside the gauge container. The coordinates are measured as a percentage of the container's ...
  27. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width ...
  28. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width/height. ...
  29. The location of the gauge label inside the gauge container. The coordinates are measured as a percentage of the container's ...
  30. The location of the indicator inside the gauge container. The coordinates are measured as a percentage of the container's ...
  31. The locks directory needs to be specified in the 9.0 server properties (see . section in msmdsrv.ini file from Analysis Services ...
  32. The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred ...
  33. The log file '{0}' already exists. Would you like to overwrite this file or append conflict information to the end of it? ...
  34. The log file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access to it. ...
  35. The log file path "%1!s!" to the ETW target is invalid. Verify that the path exists and that the SQL Server startup account ...
  36. The log for database '%1!s!' is not available. Check the event log for related error messages. Resolve any errors and restart ...
  37. The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. An earlier log backup that ...
  38. The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. This restore sequence needs ...
  39. The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled ...
  40. The log in this backup set terminates at LSN %1!s!, which is too early to apply to the database. A more recent log backup ...
  41. The log provider "%1!s!" cannot log messages on the installed %2!s! of SQL Server. The log provider requires %3!s! or higher. ...
  42. The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed. ...
  43. The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error ...
  44. The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create ...
  45. The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, ...
  46. The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately %1!d! log records have ...
  47. The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %1!s! transactions ...
  48. The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%1!s!:%2!s!:%3!s!}, ...
  49. The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...
  50. The log reader encountered a 'CANNOT SERIALIZE TRANSACTION' error (ORA-08177) while creating an XactSet at the publisher. ...
  51. The log reader encountered a 'SNAPSHOT TOO OLD' error (ORA-01555) while creating an XactSet at the publisher. The creation ...
  52. The log reader encountered an 'OBJECT NOT FOUND' error (ORA-00942) while creating an XactSet at the publisher. The creation ...
  53. The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or ...
  54. The log shipping primary database %1!s!.%2!s! has backup threshold of %3!s! minutes and has not performed a backup log operation ...
  55. The log shipping secondary database %1!s!.%2!s! has restore threshold of %3!s! minutes and is out of sync. No restore was ...
  56. The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure ...
  57. The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Back up ...
  58. The logical file cannot be found inside the physical file. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  59. The logical primary key of the selected dimension table contains column types not supported as key columns. Clear the check ...
  60. The logical record relationship between articles "%1!s!" and "%2!s!" cannot be added because at least one of the articles ...
  61. The login '%1!s!' does not have access permission on publication '%2!s!' because it is not in the publication access list. ...
  62. The login attempt failed for "%1!s!". This error occurs when the login credentials provided are incorrect. Verify the login ...
  63. The login failed for user "%1!s!". The password change failed. An unexpected error occurred during password validation. %2!s! ...
  64. The login failed for user "%1!s!". The password change failed. The password does not meet the requirements of the password ...
  65. The login failed for user "%1!s!". The password change failed. The user does not have permission to change the password. ...
  66. The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. ...
  67. The login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute ...
  68. The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...
  69. The login you entered does not have the necessary permissions to save the security configuration on server instance '{0}'. ...
  70. The login you specified when connecting to server instance '{0}' has limited permissions for monitoring database mirroring. ...
  71. The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
  72. The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
  73. The lookup transform must contain at least one input column joined to a reference column, and none were specified. You must ...
  74. The Lookup transformation failed to retrieve any rows. The transform fails when the FailOnLookupFailure is set to TRUE and ...
  75. The Lookup transformation reference metadata contains too few columns. Check the SQLCommand property. The SELECT statement ...
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)