UI Translation

SQL Server 2008 R2

  1. The snapshot agent failed to create snapshot folder under the alternate snapshot folder '{0}' configured for the publication ...
  2. The snapshot agent failed to create snapshot folder under the working directory '{0}' configured for the Publisher '{1}', ...
  3. The Snapshot Agent failed to determine how much data to include in the initial snapshot. A failure may have occurred in an ...
  4. The Snapshot Agent failed to determine the partition to which a parameterized snapshot belongs. Verify that the correct parameterized ...
  5. The snapshot agent had retrieved an invalid synchronization method value of '{0}' for the publication '{1}', reconfigure ...
  6. The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined. ...
  7. The snapshot could not be generated because a required application lock could not be obtained. This lock is needed to ensure ...
  8. The snapshot folder '{0}' retrieved from the Publisher's sysmergeschemachange table does not appear to be a snapshot folder ...
  9. The snapshot for this publication has become obsolete. The snapshot agent needs to be run again before the subscription can ...
  10. The SOAP endpoint can be in either a started, stopped or disabled state. Returns TRUE if at least one SOAP endpoint is responding ...
  11. The SOAP headers on the request have exceeded the size limits established for this endpoint. The endpoint owner may increase ...
  12. The SOAPAction value is not valid. The expected format is "SOAPAction=method-uri#method-name" or "SOAPAction=method-uri/method-name". ...
  13. The sort expressions for the {2} {3}' of the {0} {1}' are different from the group expressions. In area charts with scalar ...
  14. The sort failed due to a stack overflow while sorting an incoming buffer. Please reduce the DefaultBufferMaxRows property ...
  15. The sort string for type concept "{0}" in type "{1}" is invalid or contains references to non-existent identifier parts or ...
  16. The Sort transformation cannot create an event to communicate with its worker threads. Not enough system handles are available ...
  17. The sorting applied to the {2} of the {0} {1}' is different from the grouping expression. Since the chart type is a line ...
  18. The source attribute for the classified '%{structureCol/}' OLAP mining structure column is not part of a natural hierarchy ...
  19. The source attribute of a non-key OLAP mining structure column must be related to the source attribute of the key column ...
  20. The source connection "%1!s!" must specify a SQL Server instance with a version earlier than or the same as the destination ...
  21. The source database collation ({0}) does not match the target database collation ({1}). This mismatch can cause errors when ...
  22. The source database you have selected contains no visible tables or views. Please go back to the Choose a Data Source page ...
  23. The source file is not valid. The source file is returning a count of more than 131,072 columns. This usually occurs when ...
  24. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  25. The source lineage id '%1!d!' specified for property '%2!s!' on output column '%3!s!' was not found in the input column collection. ...
  26. The source object %1!s!].[%2!s! on the non-SQL Server Publisher was either not found or is not supported. If the object exists, ...
  27. The source or the destination component contains multiple inputs or outputs. Select an input and an output to connect the ...
  28. The source Windows domain login {0} cannot be transferred across domains as {1} using the attach method since the database ...
  29. The source Windows local login {0} cannot be transferred across instances as {1} using the attach method since the database ...
  30. The source Windows local login {0} cannot be transferred across machines as {1} using the attach method since the database ...
  31. The spatial data for layer '{2}' in the {0} '{1}' is not valid. Specify spatial data that is data type SqlGeometry or SqlGeography. ...
  32. The spatial data in the specified map layer does not have any non-spatial data field that can be joined with analytical data. ...
  33. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  34. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will not ...
  35. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will only ...
  36. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the spatial type columns of the base table ...
  37. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) contains rows that were not produced by the view definition. ...
  38. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) does not contain all rows that the view definition ...
  39. The spatial reference identifier (SRID) is not valid. The specified SRID must match one of the supported SRIDs displayed ...
  40. The specified @job_type, %1!s!, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate ...
  41. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Probability'. Column=%{ColumnName/}]. ...
  42. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityStddev'. ...
  43. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityVariance'. ...
  44. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Stddev'. Column=%{ColumnName/}]. ...
  45. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Support'. Column=%{ColumnName/}]. ...
  46. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Variance'. Column=%{ColumnName/}]. ...
  47. The specified batch separator contains invalid characters. Check the batch separator and then try again. Spaces are not allowed ...
  48. The specified breakpoint ID already exists. This error occurs when a task calls CreateBreakpoint with the same ID multiple ...
  49. The specified clustered upgrade is not currently supported. This cluster upgrade will be supported by the final release of ...
  50. The specified column set value causes the estimated row size to be at least %1!s! bytes. This exceeds the maximum allowed ...
  51. The specified connection "%1!s!" is either not valid, or points to an invalid object. To continue, specify a valid connection. ...
  52. The specified connection string is not valid. Do you want to reset the connection string? If you click OK, the existing connection ...
  53. The specified connection string uses SQL Server Authentication. The FILESTREAM Provider requires Windows Authentication (Integrated ...
  54. The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for ...
  55. The specified credentials that were provided for the SQL Server service are not valid. To continue, provide a valid account ...
  56. The specified custom schema suffix is a zero-length string or contains invalid characters. Specify valid characters for the ...
  57. The specified data set folder is not valid. Specify a value for the TargetDatasetFolder property in the deployment settings. ...
  58. The specified data source folder is not valid. Specify a value for the TargetDataSourceFolder property in the deployment ...
  59. The specified database does not exist. You must choose an initialization option that creates the database when restoring ...
  60. The specified database folder '%{filename/}' is not valid. It does not match the Analysis Services naming convention of 'ID.version.db'. ...
  61. The specified delimiters do not match the delimiters used to build the pre-existing match index "%1!s!". This error occurs ...
  62. The specified disk resource '{0}' is not a valid cluster physical disk resource name. To continue, specify a valid disk resource ...
  63. The specified drive is FAT32 file system. It is recommended that you install SQL Server on a NTFS file system as it is more ...
  64. The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 R2 ...
  65. The specified feature '{0}' is not supported when running the PREPAREIMAGE action, since it does not support SysPrep. Remove ...
  66. The specified filegroup '%1!s!' is not a valid filegroup for database '%2!s!'. Specify a valid existing filegroup or create ...
  67. The specified FILESTREAM share name already exists. You should delete the share if it exists or specify a different share ...
  68. The specified FILESTREAM share name does not match the file share resource of the current failover cluster. Change the FILESTREAM ...
  69. The specified FILESTREAM share name is not a valid Windows share name. Verify that the share name is a valid Windows share ...
  70. The specified filter returns more members than can be displayed. Only the first {0} members are displayed. Consider specifying ...
  71. The specified folder is not valid. Specify a value for the TargetReportItemFolder property in the deployment settings. If ...
  72. The specified folder uses a special share name that can usually be accessed only by a login with administrative privileges ...
  73. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". Do you want to ...
  74. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". The preview cannot ...
  75. The specified holdout parameters, HoldoutMaxPercent=%{holdoutmaxpercent\}, HoldoutMaxCases=%{holdoutmaxcases\}, will cause ...
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)