During the database upgrade process on database '%1!s!', a user object '%2!s!' named '%3!s!' was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state.
During redoing of a logged operation in database '%1!s!', an error occurred at log record ID %2!s!. Typically, the specific ...
During restore restart, an I/O error occurred on checkpoint file '%1!s!' (operating system error %2!s!). The statement is ...
During rollback, the following process did not hold an expected lock: process %1!s! with mode %2!s! at level %3!s! for row ...
During startup of warm standby database '%1!s!' (database ID %2!s!), its standby file ('%3!s!') was inaccessible to the RESTORE ...
During the database upgrade process on database '%1!s!', a user object '%2!s!' named '%3!s!' was found to already exist. ...
During the database upgrade, the full-text filter component '%1!s!' that is used by catalog '%2!s!' was successfully verified. ...
During the database upgrade, the full-text protocol handler component '%1!s!' that is used by catalog '%2!s!' was successfully ...
During the database upgrade, the full-text word-breaker component '%1!s!' that is used by catalog '%2!s!' was successfully ...
During undo of a logged operation in database '%1!s!', an error occurred at log record ID %2!s!. The row was not found. Restore ...