Known data comparison issues

There are some known problems that may abort data comparison process:

  • When you are working with Azure, you can get the “A transport-level error has occurred when receiving results from the server. (provider: TCP provider, error: 0 - An existing connection was forcibly closed by the remote host.)” error, and the comparison process will be aborted. This problem occurs because Azure closes connection.

When a connection is opened, a connection pool that stores low-level connections and keeps them open to reduce performance loss when re-opening these connection is created. dbForge Studio for SQL Server uses the ADO.NET model for data access, where pool timeout is 10 minutes, whereas Azure closes low-level connections after 5 minutes timeout. That’s why you get the above message when trying to access data.

Microsoft ADO.NET developers should correct such behaviour.

Want to Find out More?

Overview

Overview

Take a quick tour to learn all about the key benefits delivered by dbForge Studio for SQL Server.
All Features

All features

Get acquainted with the rich features and capabilities of the Studio in less than 5 minutes.
Request a demo

Request a demo

If you consider employing the Studio for your business, request a demo to see it in action.
Ready to start using dbForge Studio for SQL Server?