Answered by:
Database mirroring goes into synchronizing mode for a long time

Question
-
Hi,
I am using sql server 2008 with sp3. I have 15 databases which are configured for mirroring on a single instance of sql server. But in 4 databases out of 15, mirroring status is showing as Synchronizing from long time..
Mark As Answer If My Reply Is Helpful<br/> Thanks<br/> Neeraj Bhandari (MCTS - Sql Server 2008)
Tuesday, November 5, 2013 4:41 AM
Answers
-
Hi Neeraj,
If the network link is unreliable between the principal and mirror, you may see the mirroring state switching back-and-forth between SYNCHRONIZING and SYNCHRONIZED
OR
Chances of principal generating the transaction log faster than the log can be sent to the mirror ..
By the way to my knowledge Microsoft recommended databases mirroring configuration on instance is not more than 9 databases that's the best practice . That's what i read in one of the article.
------------------
Thanks,Suhas Vallala- Marked as answer by Sofiya Li Monday, November 11, 2013 2:55 AM
Tuesday, November 5, 2013 8:05 AM -
Hi Neeraj,
During a database mirroring session, the mirrored database is always in different specific state (the mirroring state). For example, At the start of a database mirroring session, the database is in the SYNCHRONIZING state. The principal server is serving the database, and the mirror is trying to catch up.
According to your description, mirroring status is showing as synchronizing from long time. We need to verify if there are some failures after the synchronizing state is changed synchronized. Or it just be more time for changing the state. There are many factors can affect the database mirroring session. For example, consuming inordinate CPU and/or memory, network traffic , blocked processes or an anti-virus software and so on.
There is a detail about monitoring Database Mirroring, you can review them and check if the mirroring process can run well during a mirroring session.
http://technet.microsoft.com/en-us/library/ms190030.aspxThanks,
Sofiya Li- Marked as answer by Sofiya Li Monday, November 11, 2013 2:55 AM
Wednesday, November 6, 2013 6:39 AM
All replies
-
http://support.microsoft.com/kb/924686
http://technet.microsoft.com/en-us/magazine/2009.06.sqlqa.aspx
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
- Edited by Uri DimantMVP Tuesday, November 5, 2013 7:38 AM
- Proposed as answer by Sofiya Li Wednesday, November 6, 2013 6:09 AM
Tuesday, November 5, 2013 7:32 AM -
Hi Neeraj,
If the network link is unreliable between the principal and mirror, you may see the mirroring state switching back-and-forth between SYNCHRONIZING and SYNCHRONIZED
OR
Chances of principal generating the transaction log faster than the log can be sent to the mirror ..
By the way to my knowledge Microsoft recommended databases mirroring configuration on instance is not more than 9 databases that's the best practice . That's what i read in one of the article.
------------------
Thanks,Suhas Vallala- Marked as answer by Sofiya Li Monday, November 11, 2013 2:55 AM
Tuesday, November 5, 2013 8:05 AM -
Hi Neeraj,
During a database mirroring session, the mirrored database is always in different specific state (the mirroring state). For example, At the start of a database mirroring session, the database is in the SYNCHRONIZING state. The principal server is serving the database, and the mirror is trying to catch up.
According to your description, mirroring status is showing as synchronizing from long time. We need to verify if there are some failures after the synchronizing state is changed synchronized. Or it just be more time for changing the state. There are many factors can affect the database mirroring session. For example, consuming inordinate CPU and/or memory, network traffic , blocked processes or an anti-virus software and so on.
There is a detail about monitoring Database Mirroring, you can review them and check if the mirroring process can run well during a mirroring session.
http://technet.microsoft.com/en-us/library/ms190030.aspxThanks,
Sofiya Li- Marked as answer by Sofiya Li Monday, November 11, 2013 2:55 AM
Wednesday, November 6, 2013 6:39 AM