Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Okay, thanks. I don't currently have multiple servers to test the replication, but I know that it's a future goal so I wanted to design the tables with that in mind.
(Sorry, didn't mean to hit enter) In an even more simplified example, if the table is (C1 (PK), C2 (NON-UNIQUE CLUSTERED), (UNIQUIFIER(hidden from user)), on P1 the row is (1, 1, NULL) on P2 the row is (2, 1, NULL). When these are merged onto the subscriber the rows will be (1, 1, ???), (2, 1, ???). The uniqueness of the PK is preserved, but what will happen to the uniquifier value?
Right, but the primary key is unique. My concern is that the clustered index must also be unique (and SQL Server will force it to be unique if not declared as unique).
