Adjust database compatibility downgrade solve application does not support high-version SQL Server

We once encountered a problem where our database was of a higher version, but the developers said their software was not good at supporting the database of a later version. At that time I asked them if they were using any special features, such as the features in the old version of SQL Server and not supported in the new version, they are sure there is no, just used the development of T-SQL. I guess it should

We once encountered a problem where our database was of a higher version, but the developers said their software was not good at supporting the database of a later version. At that time, I asked them if they were using any special features, such as those in the old version of SQL Server but not supported in the new version. They are definitely not, only use the development of T-SQL. I guess it should

We once encountered a problem where our database was of a higher version, but the developers said their software was not good at supporting the database of a later version.

At that time, I asked them if they were using any special features, such as those in the old version of SQL Server but not supported in the new version. They are definitely not, only use the development of T-SQL. I guess some old SQL statements cannot be run in the new version.

If it's just a problem with the T-SQL, you can try to downgrade the database (such as 100-90) so that the higher version of the database can be compatible with the previous T-SQL.

After the downgrade is completed, all functions are tested and no problem is found.

This is an idea. Of course, downgrading does not necessarily solve all the problems. For example, the functions used in the application are complicated, the new server is completely unsupported (for example, Notification service is unavailable in Versions later than 2008)

.

If you downgrade the compatibility level, it is very effort-saving to solve the problem.