June 7, 2013 at 5:27 am
We did a performance audit on the system and the reports revealed we should change the Clustered index (the primary key of the table) to another index, but kept the primary key on the original column. We ran the snapshot , but we niticed that the tabke of which we changed the primary key , does not get populated , althiugh the snapshot shows that records were bulkcopied into the table . Any ideas ?
June 7, 2013 at 8:40 am
I'm not sure about what you explained.
I think you changed the table on the publisher and want the same changes on the subscriber? If so:
There is an option on the publication that defines whether schema changes on an article are replicated or not.
Generally just changing some indexes on a table has no influence on the replication itself.
If your schema changes were not transferred you have to do the changes again on the subscriber(s).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply