UI Translation

SQL Server 2008

  1. The StartName property indicates the account name under which the service runs. Depending on the service type, the account ...
  2. The StartService method attempts to place the service into its startup state. It returns one of the following integer values: ...
  3. The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for ...
  4. The statement %1!s! is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ...
  5. The statement failed because column '%1!s!' (ID=%2!s!) uses collation %3!s!, which is not recognized by older client drivers. ...
  6. The statement failed because the sql_variant value uses collation %1!s!, which is not recognized by older client drivers. ...
  7. The statement is not supported on this version of the operating system. Could not find function entry point '%1!s!' in Httpapi.dll. ...
  8. The statement, INSERT INTO . '%s{name/}'.CASES, is not valid when used with a mining model. This statement can be used only ...
  9. The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. ...
  10. The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication ...
  11. The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed ...
  12. The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use ...
  13. The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. ...
  14. The stoplist '%1!s!' already contains full-text stopword '%2!s!' with locale ID %3!s!. Specify a unique stopword and locale ...
  15. The stoplist '%1!s!' does not contain fulltext stopword '%2!s!' with locale ID %3!s!. Specify a valid stopword and locale ...
  16. The STOPPING_TOLERANCE parameter for the '%{modelname/}' model is not valid. STOPPING_TOLERANCE must be integer and greater ...
  17. The StopService method places the service in the stopped state. It returns an integer value of 0 if the service was successfully ...
  18. The stored credentials are not available for one or more data sources in this report. You might be prompted to provide credentials ...
  19. The stored procedure or scalar function cannot be specified as a FROM clause reference or as a target for an UPDATE, INSERT ...
  20. The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator. ...
  21. The Stored Procedure Resolver requires a non-null procedure name. Use sp_changemergearticle to set the resolver_info correctly. ...
  22. The Stored Procedure Resolver requires the stored procedure '%1' to return a result set that matches the column definition ...
  23. The Stored Procedure Resolver requires the stored procedure '%1' to return a result set whose row identifier matches the ...
  24. The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. ...
  25. The stream cannot be found. The stream identifier that is provided to an operation cannot be located in the report server ...
  26. The string '{0}' contains a combination of characters (', ", & ;) that cannot not be passed into a SQL Server connection ...
  27. The string literal "%1!s!" contains an illegal escape sequence of "\%2!c!". The escape sequence is not supported in string ...
  28. The string literal "%1!s!" contains an illegal hexadecimal escape sequence of "\x%2!s!". The escape sequence is not supported ...
  29. The string literal contains an illegal escape sequence. The escape sequence is not supported in string literals in the expression ...
  30. The string value that starts with '{0}.' is too long for an agent parameter of type '{1}'. The maximum length allowed is ...
  31. The string value was truncated. The buffer received a string that was too long for the column, and the string was truncated ...
  32. The structure for writeback tables constructed by previous versions of Analysis Services has been updated in Microsoft SQL ...
  33. The structure of the '{0}' dimension cannot be modified because it is a linked dimension. You can specify translations and ...
  34. The structure of the data has changed (columns were added or removed). The exceptions highlighting cannot continue and will ...
  35. The structure of the migrated database may differ from that of the source database because of changes in the data model of ...
  36. The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database ...
  37. The structure, '{0}', is not valid in the cross-validation procedure call because all its models have Key Time or Key Sequence ...
  38. The StructureColumn function returns the value of the specified scalar mining structure column for the current model case. ...
  39. The StructureColumn function returns the value of the specified table mining structure column for the current model case. ...
  40. The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML document. ...
  41. The subreport '{0}' could not be found at the specified location {1}. Please verify that the subreport has been published ...
  42. The subreport '{3}' could not be processed within parent report '{4}' due to a mismatch in execution engines. Either the ...
  43. The subreport '{3}' could not be processed. Parent report '{4}' failed to automatically republish, or it contains a Reporting ...
  44. The Subscriber '%1!s!':'%2!s!' was not marked for reinitialization at the Publisher because the subscription is either anonymous ...
  45. The Subscriber partition information string may be truncated such that only the first %1!d! characters of the string will ...
  46. The subscription '{0}' cannot be found. The subscription identifier that is provided to an operation cannot be located in ...
  47. The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not accessible. ...
  48. The subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, SubscriberDb=%5!s!) is not active ...
  49. The subscription could not be initialized using an initial snapshot because one or more tables in the subscription belong ...
  50. The subscription database was successfully attached. The subscription will be visible the next time you run Windows Synchronization ...
  51. The subscription has been marked as removed and will be absent from the list of subscriptions the next time you run Windows ...
  52. The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription. ...
  53. The subscription has expired and is no longer available. Do you want to mark the subscription for reinitialization? Reinitialization ...
  54. The subscription has expired. Mark the subscription for reinitialization and restart the Merge Agent to reinitialize the ...
  55. The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You ...
  56. The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, ...
  57. The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued ...
  58. The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure ...
  59. The subscription to publication '%1!s!' was not found but a shared agent does exist. To specify a subscription to a publication ...
  60. The subscription to publication '%1' could not be verified. Ensure that all Merge Agent command line parameters are specified ...
  61. The subscription was successfully created. The subscription will be visible the next time you run Windows Synchronization ...
  62. The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and ...
  63. The summation of all expression values in the most precise expression data type. If the expression result is integer, numeric, ...
  64. The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore. ...
  65. The synchronization agent encountered an error and failed to determine if a new snapshot must be applied during the next ...
  66. The synchronization method (@sync_method) must be '[bcp native', '[bcp character', 'concurrent', 'concurrent_c', 'database ...
  67. The syntax for calling out tokens in SQL Server Agent job steps has changed in SQL Server 2005. Instead of using square brackets ...
  68. The syntax for the 'Process' command is incorrect. The 'Bindings' keyword cannot appear under a 'Process' command if the ...
  69. The syntax for the 'Process' command is incorrect. The 'Datasource' keyword cannot appear under a 'Process' command if the ...
  70. The syntax for the 'Process' command is incorrect. The 'DatasourceView' keyword cannot appear under a 'Process' command if ...
  71. The syntax for the 'Process' command is incorrect. The 'ErrorConfiguration' keyword cannot appear under a 'Process' command ...
  72. The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, ...
  73. The syntax for the ImpersonationInfo object is incorrect. The value of the ImpersonationMode property (%{strImpMode/}) is ...
  74. The syntax of argument "/{0}" is incorrect. Either the delimiter '=' is missing or there is one or more space characters ...
  75. The syntax of the broker instance '%1!s!' is invalid. The specified broker instance is too long, the maximum size is 256 ...
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)