The multi-part identifier "xxxxxxx" could not be bound.

Posted on 2009-04-01
Medium Priority
Last Modified: 2012-05-06
I have just run my stored procedure and it failed giving the following message.

The multi-part identifier "xxxxxxx" could not be bound. [SQLSTATE 42000] (Error 4104).  The step failed.

I have checked the name of the column and It is correct, so I am not sure why it can not be bound?
Question by:Mr_Shaw
LVL 31

Assisted Solution

RiteshShah earned 400 total points
ID: 24040249
can you please paste the code? it is not column name issue.
LVL 143

Accepted Solution

Guy Hengel [angelIII / a3] earned 1600 total points
ID: 24040286
this error means that you refer to a table that is not in the FROM/JOIN list of your query.

Author Closing Comment

ID: 31565349

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Ready to get certified? Check out some courses that help you prepare for third-party exams.
MSSQL DB-maintenance also needs implementation of multiple activities. However, unprecedented errors can hamper the database management. In that case, deploying Stellar SQL Database Toolkit ensures fast and accurate database and backup repair as wel…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.

607 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question