- The database takes a long time to recover and to be online on the new Principal server.
- The database stays in "In Recovery" status for a long time and does not take on the role of the mirror database on the new mirror server. At the same time, the new Principal database is in "Principal, Disconnected" state.
Any new connection should try to obtain a shared lock to the database before actually starts executing queries against it. When a database exclusive lock is held because of an internal operation, such as database recovery for mirroring, new connections may encounter a race condition where the database is open to accept connections at the time mirroring failover starts. At this moment, the new connection will try to obtain a shared lock while the exclusive lock is held by mirroring recovery task. This problem occurs when the database mirroring is not proceeding any longer because the max number of workers is reached and occupied by the connection tasks.
The issue was first fixed in the following cumulative update of SQL Server.
ID članka: 2970421 - Poslednji pregled: 21.10.2014. - Verzija: 1