UI Translation

SQL Server 2008

  1. The database management system (DBMS) %1!s! %2!s! does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms. ...
  2. The database mirroring safety level must be FULL to manually failover database "%1!s!". Set safety level to FULL and retry. ...
  3. The database mirroring service cannot be forced for database "%1!s!" because the database is not in the correct state to ...
  4. The database name is missing. To add the name, right click on the Project name, select Properties, and then enter a database ...
  5. The database owner SID recorded in the master database differs from the database owner SID recorded in database '%1!s!'. ...
  6. The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. Remote service ...
  7. The database principal '%1!s!' cannot be used in a remote service binding because it cannot own certificates. This is a special ...
  8. The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot ...
  9. The Database Publishing Wizard allows you to generate scripts for databases and objects inside of databases. This wizard ...
  10. The database schema requires a newer version of the client library ({1}). The current library is ({0}). Install the required ...
  11. The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the ...
  12. The database to be restored was named '%1!s!'. Reissue the statement using the WITH REPLACE option to overwrite the '%2!s!' ...
  13. The database was backed up on a server running version %1!s!. That version is incompatible with this server, which is running ...
  14. The database with ID '%{dbid/}' cannot be altered from ReadWrite to ReadOnly or vice versa. The ReadWriteMode property cannot ...
  15. The database with ID '%{dbid/}' cannot be created with ReadWriteMode set to ReadOnly. A database can only be created in ReadWrite ...
  16. The database with name '%{DBName/}', ID '%{DBId/}' cannot be restored since it already exists on the server and is read-only. ...
  17. The database with name '%{DBName/}', ID '%{DBId/}' cannot be synchronized since it already exists on the target server and ...
  18. The database you have selected is not a report server database. Please select a SQL Server database that contains report ...
  19. The database {0} exists on the SQL Server. You must choose a different database or install Reporting Services into existing ...
  20. The DataPoint {2} in the {0} {1}' has the name "{3}". DataValue names cannot be null and must be unique within the DataValues ...
  21. The DataPoints in the {0} {1}' has an invalid set of {2} items. {2} names must be unique within the {2} collection for the ...
  22. The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data ...
  23. The datasource '%{datasource/}' requires an isolation level of SnapshotIsolation which is not supported by the database provider. ...
  24. The datasource in the current set of out-of-line bindings, '%{Datasource/}', contains an ImpersonationMode that cannot be ...
  25. The DataSource property of the specified DataGridView is not set to a BindingSource with a SupportsFiltering property value ...
  26. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  27. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  28. The DataType element of the binding for a mining structure column, whose content type is set to Date, must be also set to ...
  29. The datatype of the identity column of table '%1!s!' is tinyint. tinyint does not have enough numbers available for merge ...
  30. The DataType property for the {0} is {2}, but the default value Expression for "{1}" returns the data type {3}. The data ...
  31. The DataType property for the {0} is {2}, but the Expression for "{1}" returns the data type {3}. The DataType property for ...
  32. The DataType property for the {0} is {2}, but the {1} has the data type {3}. The DataType property for the Attribute must ...
  33. The DataTypeCompatibility property of ADO type connection manager "%1!s!" was set to 80 for backward compatibility reasons. ...
  34. The DataTypeCompatibility property of ADO type connection manager "{0}" was set to 80 for backward compatibility reasons. ...
  35. The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table ...
  36. The date frequency level is required. If you do not want it to be visible, you can hide this attribute in the dimension editor. ...
  37. The date part parameter specified for function "%1!s!" is not valid. It must be a static string. The date part parameter ...
  38. The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. ...
  39. The date/time is converted to the RFC1123 standard format. It follows the custom pattern 'ddd, dd MMMM yyyy HH:mm:ss G\MT'. ...
  40. The date/time is converted to the RFC1123 standart format. It follows the custom pattern 'ddd, dd MMMM yyyy HH:mm:ss G\MT'. ...
  41. The date/time is converted to the universal full format. Pattern is always the same regardless of culture or format provider. ...
  42. The date/time is converted to the universal sortable format. Pattern is always the same regardless of culture or format provider. ...
  43. The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try ...
  44. The DBCC NEWALLOC, DBCC ROWLOCK, DBCC TEXTALL, and DBCC TEXTALLOC commands were previously announced as deprecated and have ...
  45. The DBMS type or version of "%1!s!" is not supported. A connection to Microsoft SQL Server version 8.0 or later is required. ...
  46. The DDL operation is not supported for article '%1!s!'. If the column in the DDL operation is enabled for FILESTREAM or is ...
  47. The default buffer maximum rows must be larger than %1!d! rows. An attempt was made to set the DefaultBufferMaxRows property ...
  48. The default buffer size must be between %1!d! and %2!d! bytes. An attempt was made to set the DefaultBufferSize property ...
  49. The default constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it is defined on the unpublished column ...
  50. The default folder may not be accessible by synchronization agents running at the following Subscriber(s): {0}. The folder ...
  51. The default folder may not be accessible by synchronization agents running at the following Subscriber(s): {0}. The folder ...
  52. The Default Measure for the {0} perspective is not valid because it refers to a measure that is not included in the perspective. ...
  53. The default report processing timeout value, in seconds, for all reports managed in the report server namespace. This value ...
  54. The default session (progress report) trace cannot be subscribed to because the connection is not associated with an existing ...
  55. The default sort string for type "{0}" is invalid or contains references to non-existent identifier parts or property names. ...
  56. The default value Expression for the {0} contains one or more of the following: Path, Function, AttributeRef, EntityRef, ...
  57. The default value was attempted to be set for column %1!Iu!. Default values can not be set for InMemory Rowset columns. InMemory ...
  58. The DefaultAggregateAttributeID property for the {0} is specified, but the IsAggregate property is true. A default aggregate ...
  59. The DefaultAggregateAttributeID property for the {0} refers to the {2}, which is not a variation of "{1}". The default aggregate ...
  60. The defaults you have specified will initialize the properties of new articles as they are published. One or more {0} have ...
  61. The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys. ...
  62. The delete operation cannot be performed because the server has encountered more than one member in a parent-child dimension ...
  63. The delete operation involves more than 20 lines. Are you sure you wish to save the deleted text in the Undo buffer? Responding ...
  64. The delivery extension associated with this subscription is no longer installed in the system. Select a different extension ...
  65. The delivery extension associated with this subscription is not available on this report server. Verify that the delivery ...
  66. The delivery extension settings and report parameter values can use field values returned by the command or query. If there ...
  67. The delivery extension used by this subscription is no longer available on the report server. To continue, choose a new delivery ...
  68. The dependencies reported for entity "%1!s!" do not include references to columns. This is either because the entity references ...
  69. The dependent column "{1}" is contained in the determinant columns. Please remove it from the determinant columns to correct ...
  70. The dependent object '{0}' will not be considered during per-article dependencies analysis because it is of the type '{1}' ...
  71. The deployment server name has not been specified. To set the server name, right click the project name in Solution Explorer, ...
  72. The designer cannot display calculations because there are one or more syntax errors in the MDX script. To display these ...
  73. The designer window cannot be closed while a package is running. Stop the debugger before attempting to close the window. ...
  74. The destination object in a property mapping has no parent. The destination object is not a child of any sequence container. ...
  75. The destination table of the newly created relationship has no primary key defined. Would you like to define a logical primary ...
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)