Actually, this is a change for many products and software that connects to SQL Server. Updated drivers require us to now decide to trust the server certificate.
This is part of a series I have on SQL Compare from Redgate Software. It’s an amazing piece of software that you should try if you haven’t. Download an eval today.
I opened a project recently in SQL Compare 15 to check something for a friend. I went to run the compare and saw this:
At first I thought that one or both of my instances were broken, but I realized that this is a security issue. Updated drivers changed the default encryption options, which means we need to specify this.
The products at Redgate have been getting updated across the last year to add in a “trust server certificate” box. It’s not set by default, which I find annoying, as I rarely find SQL Server’s with certs. Certainly none of my test instances, and I wish I could set this to check by default.
In any case. when I check the boxes in the image above, the compare runs.
Something to keep in mind and a muscle habit to build if you still use SQL Compare often. If you don’t, give it a try. It’s amazing.
Voice of the DBA 