When comparing and/or deploying, the following error may be returned by SQL Server:

"This SQL Server has been optimized for x concurrent queries. This limit has been exceeded by x queries and performance may be adversely affected."

This may make it seem as if SQL Compare or Data Compare is making many connections to the database, however, SQL Data Compare and SQL Compare will only make a single connection to each database it is comparing.

If you want to check to see exactly what connections are being made to SQL server, by Redgate tools or other processes, you can check the current connections by running sp_who (see books online) in a query editor in the context of the master database. Using that, you should be able to see which connections are currently open and what is using them.