UI Translation

SQL Server 2008

  1. The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they ...
  2. The current Analysis Services connection does not point to a valid catalog. Click the 'Connection' button on the Analyze ...
  3. The current connection does not support the cross-validation task. A connection to an Enterprise Edition instance of Analysis ...
  4. The current edition of SQL Server cannot be upgraded because some of the specified features are not supported in the SQL ...
  5. The current event was not reported to the Windows Events log. Operating system error = %1!s!. You may need to clear the Windows ...
  6. The current instance of SQL Server cannot be upgraded because it is running on a domain contoller and the service account ...
  7. The current instance of SQL Server cannot be upgraded because there are databases attached with FILESTREAM filegroups and ...
  8. The current instance of the SQL Server Analysis Services service cannot be upgraded because the Analysis Services service ...
  9. The current log shipping configuration is not functional because the required backup job cannot be found. You must drop the ...
  10. The current login '%1!s!' is not in the publication access list (PAL) of any publication at Publisher '%2!s!'. Use a login ...
  11. The current login does not have permissions to set the database owner to '{0}' The database was created successfully however. ...
  12. The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session ...
  13. The current monitor is not functional because the required alert job cannot be found. You can recreate the alert job by running ...
  14. The current node {0} is at patch level {1}], which is lower than that of active node {2}: patch level {3}]. After completing ...
  15. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  16. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  17. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  18. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  19. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  20. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  21. The current number of message fragments received in transport receive I/O operations that have not been enqueued (or rejected) ...
  22. The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer. ...
  23. The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being ...
  24. The current package settings are not supported. Please change the SaveCheckpoints property or the TransactionOption property. ...
  25. The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH ...
  26. The current security context cannot be reverted using this statement. A cookie may or may not be needed with 'Revert' statement ...
  27. The current security context cannot be reverted. Please switch to the original database where '%1!s!' was called and try ...
  28. The current selection contains more than one row. To run this task, please make sure that your selection contains only one ...
  29. The current selection is not valid for cross-validation. All the selected models have Key Time or Key Sequence columns. Select ...
  30. The current task requires a predictable attribute. The specified attribute, '%{Attribute/}', of the '%{Model/}' mining model ...
  31. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. ...
  32. The current tuning session has already been scheduled to run at {0}. If you choose another option, previous schedule will ...
  33. The current user %1!s! does not have SELECT permission on the table %2!s!. The user must have SELECT permission to retrieve ...
  34. The current user '%1!s!' does not have a valid linked server login mapping for non-SQL Server Publisher %2!s!]. Replication ...
  35. The current user ('%1!s!') either does not have permission to access the database specified in the parameter @execute_query_database ...
  36. The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use G ...
  37. The CurrentCube property on the Context object cannot be used since there is no available cube context. This typically occurs ...
  38. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  39. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  40. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  41. The currently selected partitions have different error configurations. Any changes made will be applied to all selected partitions. ...
  42. The currently selected partitions have different proactive cache configurations. Any changes made will be applied to all ...
  43. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  44. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  45. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  46. The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction ...
  47. The custom command name %1!s! specified for parameter %2!s! will be ignored. A system generated name will be used instead. ...
  48. The custom component shape with the Prog ID '{0}' could not be created. The designer will attempt to use the generic shape ...
  49. The custom event "%1!s!" is already declared with a different parameter list. A task is trying to declare a custom event, ...
  50. The custom property "%1!s!" cannot be specified for the aggregation type selected for this column. The comparison flags custom ...
  51. The custom stored procedure calling the format for the %1!s! command specified in the article definition does not match the ...
  52. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a CustomReportItem must have the ...
  53. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must ...
  54. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must ...
  55. The CustomReportItem {3}' has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for ...
  56. The CustomReportItem {3}' has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for ...
  57. The data could not be uploaded because the data types for column, "{0}", are not consistent. SAP data type: {1}; Integration ...
  58. The data could not be uploaded because the decimals for column, "{0}", is not consistent. SAP decimals: {1}; Integration ...
  59. The data could not be uploaded because the InfoObject for column, "{0}", is not consistent. SAP InfoObject: {1}; Integration ...
  60. The data could not be uploaded because the length for column, "{0}", is not consistent. SAP length: {1}; Integration Services ...
  61. The data could not be uploaded because the number of columns in SAP and the number of columns in Integration Services are ...
  62. The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the ...
  63. The data extension used for the {0} {1}' failed to detect the default collation properties for the connection. Details: {3} ...
  64. The data file "%1!s!" already exists at the specified location. Cannot overwrite the file as the Overwrite option is set ...
  65. The data file "{0}" already exists at the specified location. Cannot overwrite the file because the overwrite option is set ...
  66. The Data Flow changed the size of a buffer away from the default values. The event text includes the sizes and the reasons. ...
  67. The data flow component provided a duplicate friendly name '{0}' for property '{1}'. Contact the component vendor for more ...
  68. The data flow component provided an empty name when retrieving a friendly name for value '{0}' of property '{2}'. Contact ...
  69. The data flow component provided duplicate value '{0}' when retrieving friendly names for property '{1}'. Contact the component ...
  70. The Data Flow engine scheduler cannot allocate enough memory for the execution structures. The system was low on memory before ...
  71. The Data Flow engine scheduler cannot retrieve object with ID %1!d! from the layout. The Data Flow engine scheduler previously ...
  72. The Data Flow engine scheduler failed to create a thread object because not enough memory is available. This is caused by ...
  73. The Data Flow engine scheduler failed to reduce the execution plan for the pipeline. Set the OptimizedMode property to false. ...
  74. The Data Flow engine scheduler failed to retrieve the execution tree with index %1!d! from the layout. The scheduler received ...
  75. The Data Flow task encapsulates the data flow engine that moves data between sources and destinations providing the facility ...
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)