→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
We recently migrated our Lansweeper database from SQL Server 2012 to a new server with SQL Server 2017. The database was first created on the SQL 2012 server and therefore was automatically assigned a database compatibility mode setting of 110 (the value for SQL 2012). Now that the database has been migrated to SQL Server 2017, should the compatibility mode setting be updated to 140 (the value for SQL 2017)? Or should it stay where it is?

We are running Lansweeper and have not had any issues. The closest question to this one I could find was the one linked below. The poster basically had the same question and there were some responses but no one actually answered the question.


Thank you in advance ...


New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now