June 23, 2008 at 4:41 am
Hello,
I am currently working on a database mirroring setup for 10 databases each under 5 GB.
When i enable mirroring on the Principal server, even before i actually start mirroring databases i noticed that network wait increases. I am using Quest Performance Analysis to monitor my Principal and my Mirror.
I haven't found documentation on this type of wait (DBmirror Events Queue, DBmirror CMD) and don't know if I should be concerned or if this is normal.
As i try to add new databases for mirroring i noticed that these wait events increase and at 5-6 databases network workload starts to be a problem as it rises to 80-90% although performance monitor on both mirror and principal report a maximum of 200 KB / sec transfer.
Both Principal and Mirror have a Gbit network card and they're both in the same private lan.
If you have any suggestions on what i should monitor please give me a hint.
Here is a screenshot of what Q. Perf. Analysis signals as a network performance problem.
Thank you.
June 23, 2008 at 1:16 pm
Here are some resources that might help:
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
Based on my experience, mirror-related wait states do increase as you mirror more databases, but how much is too much is not often easy to answer without experimentation.
Brad M. McGehee
DBA
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply