CODEWITHSUNDEEP
databasevisual-studio-2012sql-server-data-tools
Adel Khayata
Adel Khayata

Reputation: 2836

VS 2012 Database Project "unresolved reference to object" Error

I created SQL Server Database Project in VS 2012 & imported our database. When I build the project, I get a lot of "unresolved reference to object" Errors. These errors are only for a few views I have in my database. The syntax for these views are correct & I am not using temp tables. What should I check to solve this issue?

UPDATE: This is one example:

    CREATE view [Factory].[NonStartedOrders]
as
 SELECT 

"Customers"."CustomerName", "Customers"."CustomerAName",
"Customers"."MarketID",
"Orders"."OrderID", 
"Orders"."ApproveDate", 
"FactoryOrders"."FactoryID", 
"FactoryOrders"."EstEndDate", 
"FactoryOrders"."StatusID", 
"FactoryOrders"."TotalWeight", 
"Karats"."KaratEName"

FROM   (("Taiba"."Sales"."FactoryOrders" "FactoryOrders" 
INNER JOIN "Taiba"."Sales"."Orders" "Orders" ON "FactoryOrders"."OrderID"="Orders"."OrderID") 
INNER JOIN "Taiba"."General"."Customers" "Customers" ON "Orders"."CustomerID"="Customers"."CustomerID") 
INNER JOIN "Taiba"."MasterPiece"."Karats" "Karats" ON "Orders"."MKaratID"="Karats"."KaratID"

"Taiba" here is my database name. I am getting 30 errors only for this view. These are a few errors of them:

Error   217 SQL71561: View: [Factory].[NonStartedOrders] has an unresolved reference to object [Taiba].[Sales].[FactoryOrders]

Error   219 SQL71561: View: [Factory].[NonStartedOrders] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [Taiba].[Sales].[FactoryOrders].[FactoryOrders]::[OrderID], [Taiba].[Sales].[FactoryOrders].[OrderID] or [Taiba].[Sales].[Orders].[FactoryOrders]::[OrderID].

Upvotes: 49

Views: 90026

Answers (12)

Michał Jełowicki
Michał Jełowicki

Reputation: 11

In my case it was just a single column which had space at the end of the name - [hasWorkspaceLevelSettings ]. Putting it in square bracket solved the issue.

Upvotes: 1

IngoB
IngoB

Reputation: 2989

Or, to make Sorensen's answer a bit easier to understand/implement: Drop the "Database variable"

enter image description here

by deleting and recreating the database reference. I need to say though that it solved my problem but I don't know what the database variables are needed for. Might be needed sometimes, they exist for some reason. :)

Upvotes: 5

Adel Khayata
Adel Khayata

Reputation: 2836

I solved this issue.

It seems a few of my views/SPs have referenced the tables using this naming convention ( 3 parts qualified name ):

DatabaseName.SchemaName.TableName

I changed all references to be as the following:

SchemaName.TableName

Upvotes: 32

colbybhearn
colbybhearn

Reputation: 482

I have a DacPac project containing objects which use three part naming to refer to the containing database (hundreds of instances such as [thisDb].[dbo].[obj]* exist). I need compare and update this database, but the db project fails to build due to 200+ sql71561 errors.

I did not want to remove the unnecessary database name part or switch to using a database name variable. To successfully build, (properly) compare, and then update a database using three part naming or fully qualified naming to refer to itself, there is a way to pacify visual studio:

  1. Create a copy of the original db project.
  2. In the copy db project, update all local database object references to use just two part names ([dbo].[obj]) instead of three part names (I used find & replace).
  3. Make sure the copy db project targets the same SQL server version and builds successfully.
  4. Reference the copy db project from the original db project (whether via database variable, database name only, or dacpac).
  5. The original db project can now build because its references can be resolved.
  6. The original db project can now be used to update the actual database in SQL Server after a compare.
  7. A recompare after the update shows a flawless victory.

Upvotes: 1

Sorensen
Sorensen

Reputation: 871

To reference another sqlproj's schema and use three-part naming, modify your .sqlproj file to add a DatabaseVariableLiteralValue element on the referenced project.

In within the element like <ProjectReference Include="..\SomeDatabaseProject\SomeDatabaseProject.sqlproj">, add the following:

<DatabaseVariableLiteralValue>SomeDatabaseProject</DatabaseVariableLiteralValue>

For example:

    <ProjectReference Include="..\SomeDatabaseProject\SomeDatabaseProject.sqlproj">
      <Name>SomeDatabaseProject</Name>
      <Project>{some-project-guid}</Project>
      <Private>True</Private>
      <DatabaseVariableLiteralValue>SomeDatabaseProject</DatabaseVariableLiteralValue>
    </ProjectReference>

Then you can use clean, three-part naming references like SomeDatabaseProject.SomeSchema.SomeTable.

Upvotes: 9

Fetchez la vache
Fetchez la vache

Reputation: 5230

This may be an edge case but if in your object definition you are also documenting the object (we do, anyway...) using sp_addextendedproperty you can also get this error if you have stated an incorrect object type - which can happen if copy & pasting. The "unresolved reference to object" error makes sense here when you think about it.

For example the following will recreate the error as the level1type should be 'PROCEDURE' and not 'FUNCTION'.

EXEC sp_addextendedproperty
  @name = N'MS_Description',
  @value = N'Description of the stored procedure...',
  @level0type = N'SCHEMA',
  @level0name = N'dbo',
  @level1type = FUNCTION',
  @level1name = N'spMyStoredProcedureName'
GO

Upvotes: 1

Nilanjan Pal
Nilanjan Pal

Reputation: 21

It is possible that the objects are inside NotInBuild tag in the project file for naming or other issue. In my case I saved the file with ..sql and the extra dot was causing it to move under NotInBuild tag inside project file. I corrected the extension and moved the missing object under build tag and that resolved the issue.

Upvotes: 2

Dev
Dev

Reputation: 1541

You will also get this error when you add a table (using .sql file ) and if you do not check-in the .sqlproj file

Upvotes: 1

ClarenceG
ClarenceG

Reputation: 163

This happened to me when building a CTE in Visual Studio 2015. I changed the Build Action to Compile and the errors went away.

  1. Select the file(s) with the error
  2. Press F4 to see the properties.
  3. Select 'Compile' in the Build Action drop down list.

Hope this helps someone.

Upvotes: 13

fiat
fiat

Reputation: 15981

In my case, the function that couldn't be found was of Build Action=None and so it wasn't being included in the compile.

Changing the Build Action to Build corrected this.

Upvotes: 19

superlogical
superlogical

Reputation: 14960

Try explicitly defining the class:

class: Specifies the class of the securable on which the permission is being granted. The scope qualifier :: is required.

Read the docs on the SQL GRANT statement: http://technet.microsoft.com/en-us/library/ms187965.aspx

In my case I had a User Defined Table Type.

GRANT EXECUTE ON TYPE::[dbo].[MessageTableType] TO [PostOffice_Role];

Upvotes: 1

Gwasshoppa
Gwasshoppa

Reputation: 904

One other possibility is that the schema you have used in your view/table etc does not exist in the project. You may need to add the schema to the VS Database Project.

Right Click the project and Add > New Item > Schema

Upvotes: 47

Related Questions