Custom comparison key in SQL Source Control
When adding a static table to be managed by SSC the comparison key is automatically selected. Our tables have auto generated INT ID columns as PK used in FK's. In our Static Data tables we have other columns that are unique and for them we have UK’s that we would like to use as the comparison key.
Here is another with the same issue...
I have not found any workaround for this yet at least.
I believe that this would be a great improvement for SSC and would be used by many. If you agree please vote for this feature so that is gets attention.
Steve Schmechel commented
Same issue exists here almost 2 years later. Where is this in the feature road-map?
Bill Schoonmaker commented
The documentation seems to imply that you can use an alternate key as a comparison but I have been unable to prove this. I added a unique index to an existing table that already has a primary key then went back into link static data. I thought there would be an option to choose between the existing pk and the newly created unique key but there wasn't a way to do it. This seems to be a very much needed feature so I hope it is implemented soon.