Adding index on a replication subscriber

  • A table is replicated (transaction replication) on reporting server. For performance purpose an index is suggested on subscriber database. Could it affect the replication any way?

  • No and yes. let us say it depends on the index. If it is a normal index, No it will not have any effect. But if it is a Clustered index on Primary key, then you could have problem.

    -Roy

  • Thanks for quick reply.

    Table has clustered index already on publisher and subscriber both. The new index is non-clustered index.

  • It should not affect replication in that replication will still work. I know that you cannot add an index on any columns added by replication as that will break things (in merge scenario - haven't verified this with transactional).

    The one thing that you have to be careful of is that indexes require resources to maintain them so, they are not free and replication will be slowed in some way by having to insert into this table and then update the index. So, keep that in mind.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • It works in transactional if you have the switch on i forget where it is but - in one of the properties it is on by default....

    Should work for you....it tell you if not and say table in replication mode.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply