3

I am getting an error when using SSDT 2010 (latest updates, v10.3.21208.0) with multiple database projects in a single solution. The error reads the following:

SQL71561: View: [dbo].[View] has an unresolved reference to object [OtherDatabase].[dbo].[OtherTable]

I've read all the other resources I could find on Stack Overflow and Google. Here are some things I've already tried:

  • Setup Database References to the other projects within the solution.
  • Cleared out the Database variable option to bypass the SQLCLR variable that dynamically changes your database name based on configuration options.
  • Ensured that Enable extended Transact-SQL verification for common objects is disabled on all projects
  • Have the Database location option set to: Different database, same server
  • Ensured the Project Build Order is arranged logically
  • Tried the suggestions from this post

Nothing seems to be working for me. Any help would be much appreciated. Here is a screenshot that might shed more light on my problem:

Image showing my visual studio window with the error

Improve this question
1
  • I removed the reference from my project and re-added it. Commented Jul 21, 2015 at 21:19

3 Answers 3

Reset to default
9

It has been a while, but I still want to share this solution with others that may be following the same lost links I was initially. Pay close attention to step 4. That cleared the issue for me.

A possible solution is to add a database reference to the database that has the missing object. The reference needs a Data-tier Application (dacpac file) that can be easily generated on the solution with the database project that has the missing object. Press the right mouse button over the database project and selected Snapshot Project. The dacpac file is created on the Snapshots folder. The file should then be copied to a common folder for re-usability.

In the project with the error press the right mouse button over the References and selected Add Database Reference. The Add Database Reference dialog appears:

  1. Select the dacpac file
  2. Select the database location. The most common option is "Different database, same server"
  3. Confirm that the Database name field is as expected
  4. Clear the "Database variable" field in the dialog. If this field has a value the queries must use this variable and not the database name
Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Thanks for taking the time to post your answer. I don't use VS anymore so I can't confirm the solution. I'm happy to mark it as the answer if someone else vouches that it works for them.
This was also an issue in VS2015 and step 4 here solved it for me.
1

If the referenced database project builds, but the reference isn't resolving, try cleaning and rebuilding the referenced project and cleaning the project doing the referencing.

Improve this answer

Comments

0

I'm using VS2015, but it might still apply. In my case, the referenced database had a "Database Variable Name" specified in the reference properties like $(SomeDb). If someone tried to refer to an item in the referenced database using the actual database name instead of the variable, we'd get a warning about an unresolved reference. Changing those to be like [$(SomeDb)].[dbo].[SomeTable] resolved the references.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.