Open andreesteve opened 3 years ago
Installing SQL Server on the machine, even if it rejects the login from SqlCompare does seem to stop the Socket Exceptions and short circuit the bug above. Ideally this can be fixed since there is no need to for SQL Server connection for this scenario.
I've had this myself so have needed to revert to using an older version or using sqlpackage. Do we know when this will be looked at?
I guess never? This project is full of not resolved bug reports.
Issue
When comparing two dacpacs located on the local file system, DacFx tries to open a SQL connection to a unexisting SQL Server database. It fails consistently with Socket Exception and this lasts for several minutes until it gives up and continues onto doing the comparison.
This is independent of the dacpacs provided. A simple dacpac with a single table compared with an empty dacpac surfaces this behavior.
The comparison is performed correctly, but the extra minutes spent trying to connect to a database that does not exist causes significant delays to the comparison process.
We use DacFx to run comparisons in our build system to verify for breaking changes, and this is adding delays to our build pipeline.
Version
Example
Call Stack
Exception