SQL Server 2008R2 database, with Complex logical relationship， has a large number of primary keys, foreign keys, constraints, identity columns, special characters, etc. upgrade to SQL Server 2016, use backup and restore operations. If the compatibility
level is changed to SQL Server 2008 (100) in the 2016 , Can you avoid all the problems of application accessing data? If not, there will be problems.
If something goes wrong after a few days of work by using 2016, what method can be used to accurately back to 2008. Due to the complexity of constraints, there are many problems in data export and import. Is there a practical fallback method to deal with this situation？
If something goes wrong after a few days of work by using 2016, what method can be used to accurately back to 2008. Due to the complexity of constraints, there are many problems in data export and import. Is there a practical fallback method to deal with this situation？
jennifar.ding