We have a new application which includes ETL scripts, R, and .NET code all actively being developed on SQL 2016 architecture.
I just recently received approval to start setting up new environments with SQL 2017.
I would like to understand if there are any code migration related changes that might need to be made for a SQL 2017 installation or would running on SQL 2017 with SQL 2016 DB compatibility mode behave the same as if it was just a SQL 2016 installation running with the full SQL 2016 (130) compatibility mode?
Reading through this link I found the following
To upgrade the SQL Server Database Engine to the latest version, while maintaining the database compatibility level that existed before the upgrade and its supportability status, it is recommended to perform static functional surface area validation of the application code in the database, by using the Microsoft Data Migration Assistant tool (DMA). The absence of errors in the DMA tool output, about missing or incompatible functionality, protects application from any functional regressions on the new target version.
Assuming this check passes, is there anything else that I should be doing or looking at?