SQL Server 2008

  1. Data mapping to column '%1' was already found in the data. Make sure that no two schema definitions map to the same column. ...
  2. Data Migration In order to migrate data, the following prerequisites must be met: The table must be converted and loaded ...
  3. Data Migration is performing required operation to copy data from Oracle database to SQL Server. This may take few moments. ...
  4. Data or literal value could not be converted to the type of the column in the data source, and the provider was unable to ...
  5. Data to be used for the Associate task of the Data Mining Client or the Shopping Basket Table Analysis Tool. You can build ...
  6. Data to be used for the Associate task of the Data Mining Client. You can build models to predict associations between categories ...
  7. Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions ...
  8. Data truncated when converting range values to the partition function parameter type. The range value at ordinal %1!s! requires ...
  9. Data type mapping from '%1!s!' to '%2!s!' does not exist. Review source and destination data type, length, precision, scale, ...
  10. data type, it cannot be migrated using Microsoft OLE DB Provider for Oracle, use Oracle Provider for OLE DB to migrate such ...
  11. Data validation failed for one or more articles. When troubleshooting, check the output log files for any errors that may ...
  12. Data-driven subscriptions cannot be created because the credentials used to run the report are not stored, the report is ...
  13. Database %1!s! is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again ...
  14. Database %1!s! is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the ...
  15. Database %1!s! was shutdown due to error %2!s! in routine '%3!s!'. Restart for non-snapshot databases will be attempted after ...
  16. Database %1!s! was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION ...
  17. Database '%1!s!' (database ID %2!s!) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement ...
  18. Database '%1!s!' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog ...
  19. Database '%1!s!' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. ...
  20. Database '%1!s!' cannot be started because some of the database functionality is not available in the current edition of ...
  21. Database '%1!s!' cannot be started in this edition of SQL Server because it contains a partition function '%2!s!'. Only Enterprise ...
  22. Database '%1!s!' cannot be started in this edition of SQL Server because part or all of object '%2!s!' is enabled with data ...
  23. Database '%1!s!' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, ...
  24. Database '%1!s!' cannot be upgraded because its non-release version (%2!s!) is not supported by this version of SQL Server. ...
  25. Database '%1!s!' does not contain any replication metadata for a row whose ROWGUIDCOL matches the value specified for the ...
  26. Database '%1!s!' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the ...
  27. Database '%1!s!' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery. ...
  28. Database '%1!s!' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access ...
  29. Database '%1!s!' was restored, however an error was encountered while replication was being restored/removed. The database ...
  30. Database '{0}' contains no objects that can be replicated with the selected publication type. Click Back to choose another ...
  31. Database '{0}' does not exist on the mirror server instance. You must restore a backup of the principal database on the mirror ...
  32. Database administrator permissions are required to execute either the Set Calculations Contingent or Set Calculations NonContingent ...
  33. Database backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), pages dumped: %4!s!, first LSN: %5!s!, last LSN: ...
  34. Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have ...
  35. Database changes were restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), first LSN: %4!s!, last LSN: %5!s!, number ...
  36. Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first ...
  37. Database diagram support objects cannot be installed when database compatibility level is set to SQL Server 7.0 or earlier. ...
  38. Database differential changes were backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), pages dumped: %4!s!, first ...
  39. Database encryption scan for database '%1!s!' cannot complete since one or more files are offline. Bring the files online ...
  40. Database Engine Tuning Advisor could not be located on this computer. Re-run Setup and make sure it is installed properly ...
  41. Database Engine Tuning Advisor will evaluate the usefulness of existing physical design structures and will follow up with ...
  42. Database Engine Tuning Advisor will recommend both clustered and nonclustered indexes, as well as indexed views to improve ...
  43. Database Engine Tuning Advisor will recommend clustered and nonclustered indexes to improve performance of your workload. ...
  44. Database error: %1!s! page %2!s! for database '%3!s!' (database ID %4!s!) is invalid. This error cannot be repaired. You ...
  45. Database error: Database %1!s! has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. ...
  46. Database file changes were restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump ...
  47. Database file differential changes were backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), ...
  48. Database file was backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), pages dumped: %5!s!, ...
  49. Database file was restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump devices: ...
  50. Database ID %1!s!, Page %2!s! is marked RestorePending, which may indicate disk corruption. To recover from this state, perform ...
  51. Database ID %1!s!. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous ...
  52. Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started ...
  53. Database Mail allows you to block attachment of files with specified extensions. Specify the prohibited extensions in a comma-separated ...
  54. Database Mail depends on Service Broker. Service Broker is not active in msdb. Do you want to activate Service Broker in ...
  55. Database Mail is a component for sending e-mail messages from the Database Engine using SMTP. Enable Database Mail stored ...
  56. Database Mail is a new component for sending e-mail messages from the Database Engine using SMTP. Enable Database Mail stored ...
  57. Database Mail is a SQL Server component that uses the Simple Mail Transfer Protocol (SMTP) to send e-mail messages. The wizard ...
  58. Database Mail is a SQL Server component that uses the Simple Mail Transfer Protocol (SMTP) to send e-mail messages. The wizard ...
  59. Database mirroring cannot be enabled because the "%1!s!" database is in emergency or suspect mode on one of the partners. ...
  60. Database mirroring cannot be enabled because the "%1!s!" database may have bulk logged changes that have not been backed ...
  61. Database mirroring cannot be enabled for the remote copy of database "%1!s!" because the database is not in a recovering ...
  62. Database mirroring could not repair physical page %1!s! in database "%2!s!". The mirroring partner could not be contacted ...
  63. Database mirroring has been terminated for database '%1!s!'. This is an informational message only. No user action is required. ...
  64. Database mirroring is active with database '%1!s!' as the mirror copy. This is an informational message only. No user action ...
  65. Database mirroring is active with database '%1!s!' as the principal copy. This is an informational message only. No user ...
  66. Database mirroring is attempting to repair physical page %1!s! in database "%2!s!" by requesting a copy from the partner. ...
  67. Database Mirroring is disabled on this server due to error %1!s!. Check the errorlog and configuration for more information. ...
  68. Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature ...
  69. Database mirroring is starting %1!s! parallel redo thread(s) with database '%2!s!' as the mirror copy. This is an informational ...
  70. Database Mirroring Monitor connects to the following server instances using the indicated credentials to retrieve the status ...
  71. Database Mirroring Monitor is currently managing a connection to server instance '{0}' with different credentials than those ...
  72. Database Mirroring Monitor will automatically try to connect to the partners of the selected databases. Use the Manage Server ...
  73. Database mirroring was unable to obtain the network hostname. Operating system error %1!s! encountered. Verify the network ...
  74. Database mirroring will be suspended. Server instance '%1!s!' encountered error %2!s!, state %3!s!, severity %4!s! when it ...
  75. Database property 'IsRecursiveTriggersEnabled' has to be false for subscription databases at Subscribers that allow updatable ...