SQL Server 2012

  1. Database "%1!s!" is an auto-close database on one of the partnerswhich is incompatible with participating in database mirroring ...
  2. Database "%1!s!" is not in a recovering state which is required for a mirror database or secondary database. The remote database ...
  3. Database "%1!s!" is not in the correct state to become the primary database. The log must be restored from the previous primary ...
  4. Database "%1!s!" is read-only on one of the server instances which is incompatible with participating in database mirroring ...
  5. Database "%1!s!" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database ...
  6. Database "%1!s!" requires database logs to be restored either on the future mirror database before you can enable database ...
  7. Database %1!s! has more than %2!s! virtual log files which is excessive. Too many virtual log files can cause long startup ...
  8. Database %1!s! is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again ...
  9. Database %1!s! is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the ...
  10. Database %1!s! was shutdown due to error %2!s! in routine '%3!s!'. Restart for non-snapshot databases will be attempted after ...
  11. Database '%1!s!' (database ID %2!s!:%3!s!) was marked for standby or read-only use, but has been modified. The RESTORE LOG ...
  12. Database '%1!s!' cannot be added to availability group '%2!s!'. The database does not exist on this SQL Server instance. ...
  13. Database '%1!s!' cannot be added to availability group '%2!s!'. The database is already joined to the specified availability ...
  14. Database '%1!s!' cannot be added to availability group '%2!s!'. The database is currently joined to another availability ...
  15. Database '%1!s!' cannot be joined to or unjoined from availability group '%2!s!'. This operation is not supported on the ...
  16. Database '%1!s!' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog ...
  17. Database '%1!s!' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. ...
  18. Database '%1!s!' cannot be removed from availability group '%2!s!'. The database is not joined to the specified availability ...
  19. Database '%1!s!' cannot be started because some of the database functionality is not available in the current edition of ...
  20. Database '%1!s!' cannot be started in this edition of SQL Server because it contains a partition function '%2!s!'. Only Enterprise ...
  21. Database '%1!s!' cannot be started in this edition of SQL Server because part or all of object '%2!s!' is enabled with data ...
  22. Database '%1!s!' cannot be upgraded because '%2!s!' functionality is not available in the current edition of SQL Server. ...
  23. Database '%1!s!' cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to ...
  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 a contained database. The option 'contained database authentication' setting is 0. Users with passwords ...
  27. Database '%1!s!' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the ...
  28. Database '%1!s!' is enabled for database mirroring or has joined an availability group. The name of the database cannot be ...
  29. Database '%1!s!' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery. ...
  30. Database '%1!s!' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access ...
  31. Database '%1!s!' on server '%2!s!' is not currently available. Please retry the connection later. If the problem persists, ...
  32. Database '%1!s!' was restored, however an error was encountered while replication was being restored/removed. The database ...
  33. Database '{0}' cannot be joined to availability group '{1}'. The database is not an availability database on the availability ...
  34. Database '{0}' contains no objects that can be replicated with the selected publication type. Click Back to choose another ...
  35. Database '{0}' does not exist on the mirror server instance. You must restore a backup of the principal database on the mirror ...
  36. Database administrator permissions are required to execute either the Set Calculations Contingent or Set Calculations NonContingent ...
  37. Database backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), pages dumped: %4!s!, first LSN: %5!s!, last LSN: ...
  38. Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have ...
  39. Database changes were restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), first LSN: %4!s!, last LSN: %5!s!, number ...
  40. Database configurations could not be downloaded. The hosting provider has not been configured to support this operation. ...
  41. Database copy failed. Either the source or the target database has become unavailable. Please drop target database and try ...
  42. Database copy failed. No more than 1 concurrent database copy from the same source is allowed. Please drop target database ...
  43. Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first ...
  44. Database diagram support objects cannot be installed when database compatibility level is set to SQL Server 7.0 or earlier. ...
  45. Database differential changes were backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), pages dumped: %4!s!, first ...
  46. Database encryption scan for database '%1!s!' cannot complete since one or more files are offline. Bring the files online ...
  47. Database Engine Tuning Advisor could not be located on this computer. Re-run Setup and make sure it is installed properly ...
  48. Database Engine Tuning Advisor will evaluate the usefulness of existing physical design structures and will follow up with ...
  49. Database Engine Tuning Advisor will recommend both clustered and nonclustered indexes, as well as indexed views to improve ...
  50. Database Engine Tuning Advisor will recommend clustered and nonclustered indexes to improve performance of your workload. ...
  51. Database error: %1!s! page %2!s! for database '%3!s!' (database ID %4!s!) is invalid. This error cannot be repaired. You ...
  52. Database error: Database %1!s! has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. ...
  53. Database file changes were restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump ...
  54. Database file differential changes were backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), ...
  55. Database file was backed up. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), pages dumped: %5!s!, ...
  56. Database file was restored. Database: %1!s!, creation date(time): %2!s!(%3!s!), file list: (%4!s!), number of dump devices: ...
  57. Database ID %1!s!, Page %2!s! is marked RestorePending, which may indicate disk corruption. To recover from this state, perform ...
  58. Database ID %1!s!. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous ...
  59. 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 ...
  60. Database Mail allows you to block attachment of files with specified extensions. Specify the prohibited extensions in a comma-separated ...
  61. Database Mail depends on Service Broker. Service Broker is not active in msdb. Do you want to activate Service Broker in ...
  62. Database Mail is a component for sending e-mail messages from the Database Engine using SMTP. Enable Database Mail stored ...
  63. Database Mail is a new component for sending e-mail messages from the Database Engine using SMTP. Enable Database Mail stored ...
  64. Database Mail is a SQL Server component that uses the Simple Mail Transfer Protocol (SMTP) to send e-mail messages. The wizard ...
  65. Database Mail is a SQL Server component that uses the Simple Mail Transfer Protocol (SMTP) to send e-mail messages. The wizard ...
  66. Database Master Key password must be at least 8 characters long, and must contain characters from three of the following ...
  67. Database mirroring could not repair physical page %1!s! in database "%2!s!". The mirroring partner could not be contacted ...
  68. Database mirroring has been terminated for database '%1!s!'. This is an informational message only. No user action is required. ...
  69. Database mirroring is active with database '%1!s!' as the mirror copy. This is an informational message only. No user action ...
  70. Database mirroring is active with database '%1!s!' as the principal copy. This is an informational message only. No user ...
  71. Database mirroring is attempting to repair physical page %1!s! in database "%2!s!" by requesting a copy from the partner. ...
  72. Database Mirroring is disabled on this server due to error %1!s!. Check the errorlog and configuration for more information. ...
  73. Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature ...
  74. Database mirroring is starting %1!s! parallel redo thread(s) with database '%2!s!' as the mirror copy. This is an informational ...
  75. Database Mirroring Monitor connects to the following server instances using the indicated credentials to retrieve the status ...