| In Microsoft SQL Server 2008, you can configure the | | | | Furthermore, the below error message is logged in |
| database mirroring between two database. It improves | | | | SQL Server Event Log:spid23s A system assertion |
| database reliability and prevent data loss situations, if | | | | check has failed. Check the SQL error log for details. |
| one database gets damaged due to any reason. In | | | | Typically, an assertion failure is caused by a software |
| case of failure, you can restore the copy of your | | | | bug or data corruption. To check for database |
| database from mirror database. However, if you | | | | corruption, consider running DBCC CHECKDB. If you |
| unintentionally remove the transaction log files on SQL | | | | agreed to send dumps to Microsoft during setup, a mini |
| database, database mirroring session is broken by | | | | dump will be sent to Microsoft. An update might be |
| principle server. After this behavior, you can not | | | | available from Microsoft in the latest Service Pack or |
| restore the data from mirror server if principle server | | | | in a QFE from Technical Support." |
| fails. It causes database corruption and require SQL | | | | Cause |
| Database Recovery to be fixed, if backup is not | | | | The problem takes place due to wrong log space |
| available. | | | | tracking on mirror database. It can also occur due to |
| As a practical instance of this problem, consider the | | | | Microsoft SQL Server database (MDF file) corruption. |
| underwritten scenario: | | | | Resolution |
| In Microsoft SQL SVR 2008 SP1 (Service Pack 1) or | | | | If the problem is caused by wrong log space tracking, |
| Microsoft SQL Server 2008, you configure mirroring | | | | download latest update on SQL Server and install it. |
| between two databases. | | | | On the other hand, if MDF corruption is causing the |
| You run ALTER DATABASE command along with | | | | problem, you need to go for SQL Recovery to sort |
| REMOVE FILE clause for removing the transaction log | | | | out the problem. |
| files of SQL Server database on principal server. | | | | SQL Recovery is potential through advanced and |
| In the above scenario, database mirroring session is | | | | effective third-party tools, known as MS SQL |
| aborted and you can not resume it. At the same time, | | | | Recovery software. The applications employ |
| you get the below assertion: | | | | advanced scanning techniques to ensure absolute and |
| "Location: "logmgr.cpp":3350 | | | | quick recovery in all cases of SQL Server database |
| Expression: headLFCB->lfcb_startOffset GetSize () * | | | | corruption. |
| (ULONGLONG)PAGESIZE" | | | | |