UI Translation

SQL Server 2012

  1. The source Windows local login {0} cannot be transferred across machines as {1} using the attach method since the database ...
  2. The spatial data for layer '{2}' in the {0} '{1}' is not valid. Specify spatial data that is data type SqlGeometry or SqlGeography. ...
  3. The spatial data in the specified map layer does not have any non-spatial data field that can be joined with analytical data. ...
  4. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  5. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will not ...
  6. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will only ...
  7. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the spatial type columns of the base table ...
  8. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) contains rows that were not produced by the view definition. ...
  9. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) does not contain all rows that the view definition ...
  10. The spatial reference identifier (SRID) is not valid. The specified SRID must match one of the supported SRIDs displayed ...
  11. The specified '%1!s!' cannot use commas (,) to separate addresses: '%2!s!'. To continue, use semicolons (;) to separate addresses. ...
  12. The specified @job_type, %1!s!, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate ...
  13. The specified account '{0}' for setting '{1}' is not a user account. Group or other identities cannot be used for the service ...
  14. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Probability'. Column=%{ColumnName/}]. ...
  15. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityStddev'. ...
  16. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityVariance'. ...
  17. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Stddev'. Column=%{ColumnName/}]. ...
  18. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Support'. Column=%{ColumnName/}]. ...
  19. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Variance'. Column=%{ColumnName/}]. ...
  20. The specified batch separator contains invalid characters. Check the batch separator and then try again. Spaces are not allowed ...
  21. The specified breakpoint ID already exists. This error occurs when a task calls CreateBreakpoint with the same ID multiple ...
  22. The specified clustered upgrade is not currently supported. This cluster upgrade will be supported by the final release of ...
  23. The specified column set value causes the estimated row size to be at least %1!s! bytes. This exceeds the maximum allowed ...
  24. The specified command is invalid because the AlwaysOn Availability Groups feature is not supported by this edition of SQL ...
  25. The specified computer name is either an empty string or is longer than %1!s! Unicode characters. Reenter the command specifying ...
  26. The specified connection "%1!s!" is either not valid, or points to an invalid object. To continue, specify a valid connection. ...
  27. The specified connection string is not valid. Do you want to reset the connection string? If you click OK, the existing connection ...
  28. The specified connection string uses SQL Server Authentication. The FILESTREAM Provider requires Windows Authentication (Integrated ...
  29. The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for ...
  30. The specified credentials that were provided for the SQL Server service are not valid. To continue, provide a valid account ...
  31. The specified custom schema suffix is a zero-length string or contains invalid characters. Specify valid characters for the ...
  32. The specified data set folder is not valid. Specify a value for the TargetDatasetFolder property in the deployment settings. ...
  33. The specified data source folder is not valid. Specify a value for the TargetDataSourceFolder property in the deployment ...
  34. The specified database does not exist. You must choose an initialization option that creates the database when restoring ...
  35. The specified database folder '%{filename/}' is not valid. It does not match the Analysis Services naming convention of 'ID.version.db'. ...
  36. The specified delimiters do not match the delimiters used to build the pre-existing match index "%1!s!". This error occurs ...
  37. The specified directory '{0}' does not match the directory of currently installed features. The features are currently installed ...
  38. The specified directory path, "{1}", for the {0} parameter either has an invalid character or a formatting problem. Specify ...
  39. The specified directory path, "{1}", for the {0} parameter is a relative path. However, the directory path must be an absolute ...
  40. The specified directory path, "{1}", for the {0} parameter is not valid because the path is a UNC path. Specify an absolute ...
  41. The specified directory, "{1}", for the {0} parameter is not valid because the directory is encrypted or is in an encrypted ...
  42. The specified directory, "{1}", for the {0} parameter is not valid because the directory is not writable. Specify a directory ...
  43. The specified directory, "{1}", for the {0} parameter is not valid because the directory is on a removable drive. Specify ...
  44. The specified directory, "{1}", for the {0} parameter is not valid because this directory is compressed or is in a compressed ...
  45. The specified directory, "{1}", for the {0} parameter is not valid because this directory is on a shared disk in a cluster. ...
  46. The specified directory, "{1}", for the {0} parameter must not be the same as "{2}". Specify a different directory for the ...
  47. The specified disk resource '{0}' is not a valid cluster physical disk resource name. To continue, specify a valid disk resource ...
  48. The specified DNS name, '%1!s!', is invalid. The length of the DNS name needs to be between 1 and 63 characters, inclusive. ...
  49. The specified drive is FAT32 file system. It is recommended that you install SQL Server on a NTFS file system as it is more ...
  50. The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version ...
  51. The specified endpoint URL '%1!s!' is invalid. Reenter the command specifying the correct URL. For information about specifying ...
  52. The specified feature '{0}' is not supported when running the PREPAREIMAGE action, since it does not support SysPrep. Remove ...
  53. The specified filegroup '%1!s!' is not a valid filegroup for database '%2!s!'. Specify a valid existing filegroup or create ...
  54. The specified FILESTREAM share name already exists. You should delete the share if it exists or specify a different share ...
  55. The specified FILESTREAM share name does not match the file share resource of the current failover cluster. Change the FILESTREAM ...
  56. The specified FILESTREAM share name is not a valid Windows share name. Verify that the share name is a valid Windows share ...
  57. The specified filter returns more members than can be displayed. Only the first {0} members are displayed. Consider specifying ...
  58. The specified folder is not valid. Specify a value for the TargetReportItemFolder property in the deployment settings. If ...
  59. The specified folder uses a special share name that can usually be accessed only by a login with administrative privileges ...
  60. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". Do you want to ...
  61. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". The preview cannot ...
  62. The specified holdout parameters, HoldoutMaxPercent=%{holdoutmaxpercent\}, HoldoutMaxCases=%{holdoutmaxcases\}, will cause ...
  63. The specified holdout parameters, HoldoutMaxPercent=%{holdoutmaxpercent\}, HoldoutMaxCases=%{holdoutmaxcases\}, will cause ...
  64. The specified ID is in the empty (or SMDL) namespace but it is not a GUID. IDs in the empty (or SMDL) namespace must match ...
  65. The specified input cannot be accepted because it contains an edge with antipodal points. For information about using spatial ...
  66. The specified input does not represent a valid geography instance because it exceeds a single hemisphere. Each geography ...
  67. The specified input does not represent a valid geography instance. Use MakeValid to convert the instance to a valid instance. ...
  68. The specified instance name does not meet the instance naming rules for SQL Server. For more information, click Help on the ...
  69. The specified instance name is already used by an existing SQL Server instance. To continue, specify a unique instance name ...
  70. The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL ...
  71. The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL ...
  72. The specified instance of SQL Server version {0} is incompatible with the SQL Server version {0} of the UCP. Managed instances ...
  73. The specified IP Address '%1!s!' is not valid in the cluster-allowed IP range. Check with the network administrator to select ...
  74. The specified IP Address, '%1!s!', is duplicated in the IP address list. Each IP address included in the listener configuration ...
  75. The specified item is not a report definition (.rdl). Specify a report by opening the tool pane and specifying the path and ...
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)