SQL Schema Comparison Error "Target is unavailable"

sql-server visual-studio-2015 visual-studio-2017
dave picture dave · May 26, 2016 · Viewed 27.7k times · Source

When comparing an SQLServer project in Visual Studio 2015 Update 2 against a database SQL Server 2012, it shows the error "Target is unavailable" or "Source is unavailable" when change the direction.

It used to work properly a couple of months ago. Is there any workaround? I couldn't find any.

Answer

Stacy Vicknair picture Stacy Vicknair · Aug 8, 2016

I have found that using username@servername as the username for connecting will fix the issue when it happens against Azure databases. I've had connections that have historically worked without doing this suddenly stop and then this has fixed it for me.

For instance, when using a login of mylogin and connecting to myserver.database.windows.net, if I instead use [email protected] as the username I won't get the "Source is unavailable" issue.

Related questions

How to add LocalDB to Visual Studio 2015 Community's SQL Server Object Explorer?

Problem I don't understand how to make LocalDB show up in the SQL Server Object Explorer. On some VMs, it shows up automatically, on some other VMs, it doesn't. Still, after googling for hours, I don't get it. Current situation …

Read More
Warning SQL71502 - Procedure <name> has an unresolved reference to object <name>

I'm getting the following warning in my Visual Studio 2013 project: SQL71502 - Procedure has an unresolved reference to object

Read More
Unable to complete operation. The supplied SqlConnection does not specify an initial catalog or AttachDBFileName

I am trying to create an App Service web app in the Azure Portal and to connect the web app to my local on-premises SQL Server database using the new Hybrid Connection feature. Created a simple ASP.NET application using …

Read More