#flo_nuernberg
Yes the reason for that is beacsuse the JET DB changes from 2008R2 to 2012R2 and so on. So you cant take that big of a jump beyond 2012R2 and upwards.
You need to first go to 2012R2 and then do then jump from there to either 2016 or skip 2016 and go to 2019.
Yes have original started with the jump from 2008R2 to 2016, that did no work out in any way. So goining for 2019 will have the same issues.
I have heard that some 2 customers have successfull made an inplace upgrade from 2008R2 to 2016, but have never self been able to have a succesfull go on that secnario. And from what I learn was a LOT of coding and hardning took place and pure luck was the reason for their success.
Some of the CU windows updates sometimes fixes/breaks stuff we all know that. and in some lucky way these customers have been able to jump inbetween and have a success inplace upgrade.