Index rebuild job on primary replica

Question

I have a rebuild index job on primary replica. When this job runs on primary replica, it rebuilds indexes on availability group databases. So, my question is, will the indexes on secondary replica AG databases also get rebuilt?

Answer 1

See https://learn.microsoft.com/en-us/answers/questions/1180524/ag-rebuild-index.

Answer 2

Hi @Chaitanya Kiran,

The behavior of index rebuild job on secondary replicas of an Availability Group (AG) depends on the configuration of the AG and the type of index rebuild operation you are performing.

If the AG is configured with synchronous-commit mode and the index rebuild job is performed on the primary replica, then the indexes on the secondary replicas will also get rebuilt in real-time as the changes are applied to the primary replica. This is because in synchronous-commit mode, all transactions must be committed on the primary and secondary replicas before they can be considered committed.

However, if the AG is configured with asynchronous-commit mode, then the indexes on the secondary replicas may not get rebuilt in real-time. This is because asynchronous-commit mode allows the secondary replicas to lag behind the primary replica in terms of transaction commits. In this case, the indexes on the secondary replicas will eventually get rebuilt, but it may take some time for the changes to propagate to the secondary replicas.

Also noticed that you mentioned the same question before. So I'll add another answer as well.

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".