We must reverse engineer all our models. Until recently I would Compare & Merge using DA 16 against the prod SQL Server 2012 instance to update the model.
Recently the databases were moved to 2017 forcing me to upgrade to DA 17.1. Now all the PK indexes show up as needing to be updated (see screen shot attached). Notice the PK...s are 'just indexes' on the left and are 'Primary Keys' on the right. The problem is, no matter how many times I try to merge, the same changes show up as outstanding. I can't actually import or apply them such that they stop showing up as differences.
Further tests show this problem occurs even on tables that did not previously exist. That is, the merge process will add a new table but after another round of compare the primary key of that new table shows up like all the existing ones - as needing adjustment. So this doesn't just affect tables added under the old version.
Hmm. interesting. Please try this and let us know if you still http://docwiki.embarcadero.com/ERStudioDA/171/en/Using_the_Compare_and_Merge_Utility ThanksAnil
That text is over 10 pages long. Was there a particular paragraph or even section that seemed relevant? I notice that the page numbers of options are off by 1. For example the stuff documented as being on Page 3 actually appears on Page 4. I notice that half or more of the options I see when using the utility are not mentioned anywhere and there are some mentioned that I can't find. The only thing superficially looks vaguely related is "Forced Matching" which applies only to model-to-model comparisons not database to model comparisons. Fortunately because the process can't be automated and there is no way I'm going to do that for 15 models with 600-900 tables each.
So, having seemingly wasted an hour re-reading something I thought I already knew (that the page was nearly worthless) I can't help but wonder what you saw in it.