Issue with suppressing errors in SSDT (SQL Server Data Tools)

Question

It looks like SSDT supports only suppressing warnings but not errors. I have many errors, all stating:

Error 4 SQL71561: View: [dbo].[x] has an unresolved reference to object [DB1].[dbo].[y].[column]

I do not want to reference DB1 in this database project, for specific reasons. I just want these errors to be ignore when I build the project. The only way I have been able to get ride of these errors is to go to each file (view) and set the Build Action to None. Suppressing TSql Warnings at the project level or the file level does not work (I'm assuming this only suppresses warnings). And, I have not set the option to treat T-SQL warnings as errors.

Is there a better approach?

Lobectomy

Any news on this one? I have the same problem at the moment. But I cannot change the build action, because it's not going to deploy the view if I change it. – Sihonn

I also could not figure out how to suppress these errors, so I added a reference to the other database to resolve the errors. See stackoverflow.com/questions/12161392 for details. – Canescent

Answer 1

I haven't found how to avoid the error without referencing DB1, but there are two options to go about it if you don't have the code for it in SSDT:

• If you have access to the live DB1, extract a .dacpac out of it using SqlPackage. Then add this .dacpac as a reference in your project.
• Create a stub project (e.g. a fake DB1) side-by-side with yours, reference it, and add the stub objects there.

I had to use option 1 with a project a while ago, which I detailed here:

http://tangodude.wordpress.com/2014/02/05/referencing-the-sql-server-data-collectors-management-data-warehouse-in-your-ssdt-database-project/

You can extract a dacpac by using this:

SqlPackage /Action:Extract /SourceServerName:YourServerNameHere /SourceDatabaseName:YourDatabaseNameHere /TargetFile:YourDatabaseNameHere.dacpac

Chromatolysis

This link is dead – Casandra

Answer 2

on the publish database dialogue box > advanced > check the 'treat verification errors as warnings'

Pitts

This doesn't remove build errors and comparisons will not work until build errors are resolved. – Phil