Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am upgrading a mirroring pair of SQL2005 Enterprise servers to SQL2008R2 Standard which has 1 thread for mirroring limitation.

As far as I understand this limitation applies to redo queue: but I don't fully understand what this means.

My question is: how do I measure the current database system to make sure I won't run into problems with this upgrade (with this 1 thread limitation)?

share|improve this question
up vote 3 down vote accepted

Under normal operations, the redo queue is close to zero. What you can do is: track your current redo counters in perfmon (SQLServer:Database Mirroring> Redo Bytes/sec,Redo Queue). With this value you will know how much of your redo log performance will be affected when switching between the SQL editions.

Note that is SQL2008 R2 EE, if you have fewer that five CPUS, SQL will still use only one thread for the redo process. So if you have four or lesser CPUs, SQL will still use a single threaded redo operation.

share|improve this answer
Thank you! It is difficult to translate bytes/sec into 1 thread. I have 4 logical CPU with SQL2005 EE - perhaps there is actually no change. – Dina Mar 8 '12 at 21:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.