title: Unresolved References to Same Database Project
body: <p>I've created a SQL Server database project in Visual Studio 2013 and imported a DACPAC taken from a production database.  When I tried to build the project I get hundreds of SQL71501 and SQL71561 errors (both of which are "unresolved reference to an object").  Examining the scripts the problem is that many views and stored procedures use three part names: [database].[schema].[object].</p>
  
  <p>It appears that Visual Studio 2013 throws this error whenever it comes across a three part name that includes the database represented by the database project.  eg If the database project represents database "MyDatabase" and a SQL script in that project includes something like <code>SELECT t.Column1 FROM MyDatabase.dbo.MyTable t</code> then VS 2013 throws either SQL71501 or SQL71561 when I build the project.</p>
  
  <p>Is there any way of suppressing unresolved reference errors that just apply to the current database?  I still want Visual Studio to throw errors for unresolved references to external databases.</p>
  
  <p><strong>EDIT, Correction:</strong> Originally stated the error code was SQL71501.  However, it appears Visual Studio throws both SQL71501 and SQL71561 errors for unresolved references to the same database.</p>