VS 2010 build database project receive SQL04151

Question

I just started working with the Visual Studio 2010 Premium database project. I must say it does indeed rock. One thing I can't figure out is how to avoid the SQL04151 warning

Procedure: [dbo].[MyProc] has an unresolved reference to object [MyDatabase].[dbo].[MyItem].

Did I miss a simple step somewhere? All I can find online involves tempdb.

If [MyDatabase] is the same database where [dbo].[MyProc] is located it might be more advantageous to remove the [MyDatabase]. (or [$(DatabaseName)].) prefixes. If you install multiple instances on the same server for say, testing or development environments, you will not get expected results and may not even realize it, because references may be broken or work when referencing the wrong instance. — JM Hicks, Jan 02 '13 at 15:34

score 14 · Answer 1 · answered Apr 05 '10 at 14:33

14

I need to substitute [MyDatabase].[dbo].[MyTable] with [$(DatabaseName)].[dbo].[MyTable]. This cleared up the warnings.

Thanks for your help.

answered Apr 05 '10 at 14:33

beezler

646
6
18

7

Marking this item as the correct answer will move it to the top of the page, which will make it easier for others to find later. – Pedro Jul 20 '10 at 15:09
Experienced exactly the same problem, this solved it, thanks. – VikingProgrammer Apr 18 '12 at 08:43

score 3 · Answer 2 · answered Apr 02 '10 at 19:05

3

In your [dbo].[MyProc] procedure you reference [MyDatabase].[dbo].[MyItem] which is probably not part of your DB project. Even though the object exists in the DB, it is not known to Visual Studio during compilation and thus yields an error.

Normally you should have the entire DB-schema in the DB-project. Otherwise I think there is something called "partial DB projects" that you can look into.

answered Apr 02 '10 at 19:05

Anders Abel

67,989
17
150
217

Actually all objects are part of the DB project. The stored procedure is in MyDatabase. I accepted the defaults when I created the project, but I expect I missed something along the way. – beezler Apr 05 '10 at 13:55

LeWoody · Answer 3 · 2013-03-22T15:10:09.847

2

MS has acknowledged this as a bug they are working on:

https://connect.microsoft.com/VisualStudio/feedback/details/543657/4151-unresolved-reference-warning-for-tempdb

edited Mar 22 '13 at 15:10

answered Jul 02 '10 at 13:02

LeWoody

3,593
4
25
31

The link is broken. Please remove the `?wa=wsignin1.0` from the end of the URL. – Bernhard Hofmann Mar 18 '13 at 08:21
I can't see how this is related? The OP did not mention tempdb. – cdonner Jul 16 '13 at 16:00

score 0 · Answer 4 · answered Mar 01 '12 at 11:17

0

Check you have set Build Action to Build on Properties pane for the specified object..

answered Mar 01 '12 at 11:17

Karsten Laursen

9
1

VS 2010 build database project receive SQL04151

4 Answers4

Linked