• sqlfriends - Friday, December 15, 2017 10:47 AM

    I agree doing it from scratch to 2017 is the best and clean approach.

    I am currently doing the upgrade process in a test environment, and later will do it on production.
    Our production server is a very robust physical server, test environment is a VM.

    We want to reuse the physical server and we don't have another good physical server available to do this at this time.
    So in the case we chose in-place upgrade. 

    That is  the reason I posted the questions.

    Thanks.

    +1 to doing a clean Installation but this is one upgrade that needs more than a test of the migration process.  Have you considered the effects of new features such as the "improved" cardinality estimator?  I point that one out in particular because it may have different effects on different databases and these effects are not always consistent across the instance landscape.

    Perhaps I have spoken somewhat out of turn and you have considered this already but IMHO, a DBA that is considering an in-place migration most probably hasn't considered other implications not necessarily related to the migration process itself......

    Regards,
    Kev