question on replication and reindexing sql 2005

[kodaksmile]

In SQL 2005 when you reindex the publisher are those commands replicated over to the subscriber in transactional replication?

 

[ptheriault]

No, Only the database that is published.


- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[kodaksmile]

Thanks - I was trying to identify what got hung up in the transaction log - it would not clear and was up over 190 gig (db is 390) thought it might have to do with the reindex because the issue hit around the same time. I know it is caused by replication. We are currently working with Microsoft to identify the issue. (showing a high latency - critical on replication)

 

[ptheriault]

Are you re-indexing the Published database?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[kodaksmile]

yes

 

[kodaksmile]

Worked with Microsoft and they are saying it is a bug in sp2 however, we are not doing an online reindex as we are still using dbcc reindex so I am not sure that is the issue. If so the resolution is cumulative patch 2 supposedly.

 

[ptheriault]

I would make the change to the ALTER INDEX statement. It may correct your problem.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[kodaksmile]

I would have except we are still using dbcc reindex. I sent Microsoft the question yesterday of how this fixes the issue when we are not using the online option (as it was not available with DBCC reindex). Sounds like it may be another bug (same symptom). I'll let you know what the response is.