Thanks Glenn, it turns out that the fix was recommended by a Microsoft person on a Forum, but they didn’t give the KB article. The issue was that Master Data Services wouldn’t upgrade from SQL Server 2014. My colleague installed SQL Server 2016 RTM CU4 on a different Server, upgraded the Master Data Services Database and then copied it over to our SQL Server 2016 SP1 CU1. It’s all working now, but it was a bit of a mismatch, and not a relevant KB article in sight.
]]>AT LAST!!! I AM SO HAPPY!!
I have so many clients and I do not have rewrite my client code!
Kudos Microsoft Kudos !
:)))))
]]>Microsoft is pretty good about putting the same fixes (where they are relevant) across the currently supported branches of the product. In other words the RTM CU release that is available at the same time as the SP1 CU release will have the same hotfixes. To be sure, just check the KB article for each CU that lists the hotfixes for each release.
]]>We are in a situation whereby we have an issue which is supposedly resolved in SQL Server 2016 RTM CU4, but we have already installed SQL Server 2016 SP1 (and now SP1 CU1) – should we expect to find that fix in there too?
Many thanks for any thoughts that you have on this subject.
Kind regards, Nigel.
]]>