I am planning to upgrade SQL 2016 instance to SQL 2017.
I have several databases showing breaking changes related to CLR assemblies and table hints, if the compatible changes to 140.
We are planning to do an inplace upgrade, I guess during this, the upgrade process will attempt to change the compatibility level to 140.
My question is, will these reported breaking changes cause the upgrade to fail to due being incompatible ?
Or will the upgrade complete successfully but the reported changes wont work anymore?
Sorry im i am not clear.
According to this link
https://blogs.msdn.microsoft.com/datamigration/2018/10/16/announcing-assessments-on-premises-sql-server-migrating-to-azure-sql-database-managed-instance-using-dma-4-1/
"DMA also identifies compatibility issues related to the following areas:
Breaking changes: The specific schema objects that may break the functionality migrating to the target database. We recommend fixing these schema objects after the database migration."
But im not sure if that means for inplace upgrade or, backup restore or rolling upgrade etc..
thanks if anyone can clarify for me..
I dont want to do the inplace upgrade and break the instance/database.
ilikefondue