My personal preference is to build a new server with New OS and A New install of SQL Server, then migrate the databases using backup and restore, or even simply...

We have been running it in production on 9 servers for some time. There are no issues that I can see or our users have reported.

Thanks Thom,

Interestingly it did find two columns
name               name            collation_name
tblAlarmHistory    AlarmMessage    SQL_Latin1_General_CP1_CI_AS
tblAlarmHistory    Note           SQL_Latin1_General_CP1_CI_AS

Changing the compatibility level to 130, made no difference, still get exactly the same errors.

Thanks for the reply.

The compatibility is set to 100 (sql 2008) which is what it was set to following the restore. The default language at the DB level...