SQL Compare 10.4.8.87 and SQL 2017

Proteo

Hi all,
We have started using SQL 2017 and we are getting a "CommandText Property has not been initialized". Can anyone confirm that this is definitely due to SQL Compare 10.4.8.87 not working with SQL 2017 DBs?

Mark,

sam.blackburn

That's correct, SQL Compare versions before 10.7 showed that (rather unhelpful) message when connecting to an unsupported SQL Server version. More recent versions of SQL Compare will treat the server as being the latest version they understand, which for SQL Compare 12 is SQL Server 2017.

If you want to be completely sure that SQL Compare works in your situation, you can download a free trial of the latest version.