UI Translation

SQL Server 2012

  1. The current package settings are not supported. Please change the SaveCheckpoints property or the TransactionOption property. ...
  2. The current query cannot be evaluated for the '%{IMBITableId/}' table, because the table contains more than two billion rows. ...
  3. The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH ...
  4. The current security context cannot be reverted using this statement. A cookie may or may not be needed with 'Revert' statement ...
  5. The current security context cannot be reverted. Please switch to the original database where '%1!s!' was called and try ...
  6. The current selection contains more than one row. To run this task, please make sure that your selection contains only one ...
  7. The current selection is not valid for cross-validation. All the selected models have Key Time or Key Sequence columns. Select ...
  8. The current state of the database '%1!s!' is not compatible with the specified FILESTREAM non-transacted access level. The ...
  9. The current task requires a predictable attribute. The specified attribute, '%{Attribute/}', of the '%{Model/}' mining model ...
  10. The current transaction attempted to update a record that has been updated since this transaction started. The statement ...
  11. The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. ...
  12. The current tuning session has already been scheduled to run at {0}. If you choose another option, previous schedule will ...
  13. The current user %1!s! does not have SELECT permission on the table %2!s!. The user must have SELECT permission to retrieve ...
  14. The current user '%1!s!' does not have a valid linked server login mapping for non-SQL Server Publisher %2!s!]. Replication ...
  15. The current user ('%1!s!') either does not have permission to access the database specified in the parameter @execute_query_database ...
  16. The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use G ...
  17. The current user does not have sufficient permissions on the instance of SQL Server to delete the data-tier application. ...
  18. The current user does not have sufficient permissions on the instance of SQL Server to delete the data-tier application. ...
  19. The current user does not have sufficient permissions on the instance of SQL Server to upgrade the data-tier application. ...
  20. The current value '%1!s!' for sequence object '%2!s!' must be between the minimum and maximum value of the sequence object. ...
  21. The current WSFC cluster quorum vote configuration is not recommended for this availability group. For more information, ...
  22. The CurrentCube property on the Context object cannot be used since there is no available cube context. This typically occurs ...
  23. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  24. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  25. The currently selected model '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  26. The currently selected partitions have different error configurations. Any changes made will be applied to all selected partitions. ...
  27. The currently selected partitions have different proactive cache configurations. Any changes made will be applied to all ...
  28. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  29. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  30. The currently selected structure '{0}' cannot be used to perform this task. Select a model, or structure containing a model, ...
  31. The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction ...
  32. The curve index n ({0}) passed to STCurveN is less than 1. This number must be greater than or equal to 1 and less than or ...
  33. The custom command name %1!s! specified for parameter %2!s! will be ignored. A system generated name will be used instead. ...
  34. The custom component shape with the Prog ID '{0}' could not be created. The designer will attempt to use the generic shape ...
  35. The custom event "%1!s!" is already declared with a different parameter list. A task is trying to declare a custom event, ...
  36. The custom package type {1} for the {0} element does not expose a public copy constructor, which is required for setting ...
  37. The custom property "%1!s!" cannot be specified for the aggregation type selected for this column. The comparison flags custom ...
  38. The custom stored procedure calling the format for the %1!s! command specified in the article definition does not match the ...
  39. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a CustomReportItem must have the ...
  40. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must ...
  41. The CustomReportItem {3}' has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must ...
  42. The CustomReportItem {3}' has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for ...
  43. The CustomReportItem {3}' has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for ...
  44. The Cyclic Redundancy Check (CRC) value generated for the retrieved availability group configuration data from the Windows ...
  45. The DAC instance name, version, and description are displayed in SQL Server Management Studio after the DAC has been registered. ...
  46. The data could not be uploaded because the data types for column, "{0}", are not consistent. SAP data type: {1}; Integration ...
  47. The data could not be uploaded because the decimals for column, "{0}", is not consistent. SAP decimals: {1}; Integration ...
  48. The data could not be uploaded because the InfoObject for column, "{0}", is not consistent. SAP InfoObject: {1}; Integration ...
  49. The data could not be uploaded because the length for column, "{0}", is not consistent. SAP length: {1}; Integration Services ...
  50. The data could not be uploaded because the number of columns in SAP and the number of columns in Integration Services are ...
  51. The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the ...
  52. The data extension used for the {0} {1}' failed to detect the default collation properties for the connection. Details: {3} ...
  53. The data feed could not be imported because PowerPivot for Excel is busy. Try again after the current operation has been ...
  54. The data file "%1!s!" already exists at the specified location. Cannot overwrite the file as the Overwrite option is set ...
  55. The data file "{0}" already exists at the specified location. Cannot overwrite the file because the overwrite option is set ...
  56. The Data Flow changed the size of a buffer away from the default values. The event text includes the sizes and the reasons. ...
  57. The data flow component provided a duplicate friendly name '{0}' for property '{1}'. Contact the component vendor for more ...
  58. The data flow component provided an empty name when retrieving a friendly name for value '{0}' of property '{2}'. Contact ...
  59. The data flow component provided duplicate value '{0}' when retrieving friendly names for property '{1}'. Contact the component ...
  60. The Data Flow engine scheduler cannot allocate enough memory for the execution structures. The system was low on memory before ...
  61. The Data Flow engine scheduler cannot retrieve object with ID %1!d! from the layout. The Data Flow engine scheduler previously ...
  62. The Data Flow engine scheduler failed to create a thread object because not enough memory is available. This is caused by ...
  63. The Data Flow engine scheduler failed to reduce the execution plan for the pipeline. Set the OptimizedMode property to false. ...
  64. The Data Flow engine scheduler failed to retrieve the execution tree with index %1!d! from the layout. The scheduler received ...
  65. The Data Flow task failed to create a buffer to call PrimeOutput for output "%3!s!" (%4!d!) on component "%1!s!" (%2!d!). ...
  66. The Data Flow task failed to create a required thread and cannot begin running. The usually occurs when there is an out-of-memory ...
  67. The Data Flow task failed to initialize a required thread and cannot begin execution. The thread previously reported a specific ...
  68. The data flow task GUID '%1!s!' and the data flow path ID string already exist for the execution ID %2!s!. Provide a data ...
  69. The data flow task identification %1!s! was not found during execution. The specified data tap file %2!s! for path %3!s! ...
  70. The data in row {0} was not committed. Error Source: {1}. Error Message: {2} Correct the errors and retry or press ESC to ...
  71. The data in the column '{0}' does not have the required content type. In a mining structure that has a Key Time column, any ...
  72. The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset '%1!s!'. The data in the data ...
  73. The Data Mining Extensions (DMX) OPENROWSET statement supports ad hoc queries using external providers. Enable ad hoc data ...
  74. The Data Mining Extensions (DMX) OPENROWSET statement supports ad hoc queries using external providers. Enable ad hoc data ...
  75. The data mining relationship cannot be defined because the designer failed to identify the source dimension for mining model. ...
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)