|
Hi Guys and Girls! I am setting up a replication solution for a customer, replicating 7 tables, but not all columns in the tables. Publisher and distributor are on SQL 2005 Std, subscriber on SQL 2008 ent. I have set in the article options for each of the published tables to replicate the clustered index, but not the non clustered ones. All columns involved in the clustered indexes are replicated in all tables. It works fine on 6 tables, but on the 7:th I get a non clustered index on the subscriber (including the correct columns thou..) instead of the exepected clustered index. I do not have any errors anywhere, and snapping again does not fix the problem. Any ideas what might be causing this? And how to fix it?
(comments are locked)
|
|
Hm. Digging deeper into this it tured out that I was a bit fast in my judgement. While dubbelchecking, it turned out that the Index I thought was the Clustered PK on this table was in fact not. In reality the table has a unique index as PK, but but it is not clustered. And I have not choosen to replicate all the columns that was included in the clustered index. So now I just have to maintain a clustered index that will go away everytime we have to reinit the replication. But I guess that serves me right for not checking properly before posting to you guys :-) Have you thought about making the index on the table clustered? Unless there is a reason not to, it is likely the best overall solution. Also, remember you can mark your own answer as accepted since you seem to have fully discovered the situation.
Mar 17 '10 at 09:41 PM
TimothyAWiseman
It is not so easy unfortunately, as that will upset the supplier of the system. Easier to make my own fix :-)
Mar 19 '10 at 05:17 AM
Steinar
(comments are locked)
|
