Viewing 3 posts - 1 through 3 (of 3 total)
Yeah but when we did Select @@version it reported it to be CU17 - would that be the case?
December 3, 2019 at 11:43 am
#3703762
We have re-installed the CU17 and this seems to have resolved the issue for us.
Not sure how CU could seemingly be installed using Select @@version it provided the most up...
December 3, 2019 at 10:26 am
#3703745
Hi, we have the exact same issue and the CU17 is already applied. When we rebuild the catalog on our secondary SQL box that works fine with no warnings. We...
December 3, 2019 at 10:08 am
#3703741