- Server A and Server B are running Microsoft SQL Server 2008 or SQL Server 2008 R2.
- You set up database mirroring between Server A and Server B.
- You execute a BULK INSERT or BCP statement on the principal database.
Note By default, the CHECK_CONSTRAINTS option is set to off when you execute a BULK INSERT or BCP statement.
- The database mirroring is broken, and the database mirroring session enters the SUSPENDED state.
Note You must reinitialize database mirroring to resolve this issue.
Note The CHECK_CONSTRAINTS ON option causes slower performance. However, the lock assert on the mirror server does not occur.
However, this compatibility information is not transferred to the mirror server. Therefore, the child transaction lock request is incompatible with the parent transaction locks on the mirror server. This scenario causes the assert on the mirror server.
Article ID: 2700641 - Last Review: 6 Aug 2012 - Revision: 1