| The wait type REDO_THREAD_SYNC is ranked #132 by Stedman Solutions and Database Health Monitor. Wait statistics, in the context of SQL Server, refer to the amount of time that a query spends waiting to access data in the database. When a client application requests data from the database, the request is placed in a queue and the client application must wait for its turn to access the data. The time that the query spends waiting is called a "wait" and is tracked by SQL Server. This information can be used to identify potential performance bottlenecks and optimize the performance of the database. Wait statistics are commonly used by database administrators to diagnose and troubleshoot performance issues in SQL Server.
What Is REDO_THREAD_SYNC?This wait type is all about SQL Server�s Always On Availability Groups, a feature that keeps your databases mirrored across multiple servers for high availability. The �REDO� part refers to the process where a secondary server (the backup copy) catches up by applying changes from the primary server�s logs. �THREAD_SYNC� means the secondary is waiting to sync up its workers�think of them as little helpers�before it can keep going. In plain terms, it�s like the backup server saying, �Hold on, I need all my team members in line before we can finish updating the copy.� It�s a pause to make sure everything stays coordinated. Why Does It Happen?You�ll see REDO_THREAD_SYNC on a secondary server in an Availability Group when it�s replaying the primary�s changes�like after a big update or during a busy period. The wait happens because those helpers (threads) need to work together, and sometimes one has to wait for the others to catch up. It�s more likely if the secondary is under pressure, like slow disks or a flood of changes coming in. It�s a normal part of keeping the backup in sync, but if this wait is piling up or taking too long, it could mean the secondary is struggling to keep pace�maybe due to hardware lag or too much redo work. How Can You Keep an Eye on It?To check if REDO_THREAD_SYNC is slowing down your secondary, you can use the Historic Waits feature in Database Health Monitor. This tool tracks wait types over time, showing you when this wait pops up�like during a heavy update�and how long it lasts. It�s like having a timeline that reveals when the backup server�s helpers are stuck waiting. Monitoring it lets you see if it�s just routine syncing or if you need to boost the secondary�s performance�like upgrading disks or tweaking the redo process. Wrapping It UpREDO_THREAD_SYNC is SQL Server�s way of pausing to get the backup server�s team in sync while it applies changes from the primary. It�s a standard step in Availability Groups, but if it�s dragging on, it�s worth a closer look. Tools like Database Health Monitor make it simple to watch this wait type and others, keeping your database setup running smoothly. Want to stay on top of your SQL Server performance? Try Database Health Monitor�a free tool from Stedman Solutions that tracks wait types and helps you spot issues fast. Download it today and keep your Availability Groups in check!
Applies toRelated WaitsREDO_THREAD_PENDING_WORKAll Wait Types |  |
