sqlsql-serversql-server-2008stored-procedures

Reputation: 12440

SQL Server: Invalid Column Name

I am working on modifying the existing SQL Server stored procedure. I added two new columns to the table and modified the stored procedure as well to select these two columns as well. Although the columns are available in the table, I keep getting this error:

Invalid column name 'INCL_GSTAMOUNT'

enter image description here

Can anyone please tell me what's wrong here?

Upvotes: 134

Answers (19)

Junior Placido

Reputation: 31

There can be many things:

First attempt, make a select of this field in its source table;
Check the instance of the sql script window, you may be in a different instance;
Check if your join is correct;
Verify query ambiguity, maybe you are making a wrong table reference

After these checks, run the T-sql script again

Image of the script SQL

Upvotes: 1

Greg Gum

Reputation: 38109

 on g.Id = s..flashCardGroupid

This line above had by accident two periods in a row which caused this error message.

Upvotes: 0

L__

Reputation: 51

I am working with Blazor and forgot to use any quotations...

SqlDataAdapter da = new($"select * from table where column = {value}", con);

needed to be

SqlDataAdapter da = new($"select * from table where column = '{value}'", con);

Thanks to Harry's answer above for sending down the right train of thought.

Upvotes: 1

chmoder

Reputation: 985

I was using DbUp to add a column to a table then in the same script an UPDATE on that column and it said "invalid column <column name>".

Breaking the two statements into separate scripts resolved the issue.

Upvotes: 0

Bug Hunter Zoro

Reputation: 1915

When this happened to me, the good old quit and re-launch SQL server management studio did the trick for me.

Upvotes: 0

Timothy Odhiambo

Reputation: 45

I experienced similar problem when running a query from the code (C#) side. The column in the table that was bringing the above error had 'default value or binding' (when I checked the table's design) already added. So I just removed the column and its corresponding value as data being inserted by the query

Upvotes: 1

gthuo

Reputation: 2566

I came here because I was getting this error. And the reason was that I was using double quotes (") instead of single quotes (') when giving values for WHERE conditions. Writing this for the future me.

Upvotes: 10

lot_styx

Reputation: 75

Not enough rep to comment, so I'll write a new answer, re: Nick Reed's answer regarding the ordering of the tables in the query.

The JOIN operation has two operands. In the ON clause, one may only refer to columns from those operands. In Nick's first example,

SELECT * FROM table1, table2 LEFT JOIN table3 ON row1 = row3; --throws an error

table2 and table3 are the operands of the JOIN, but the ON clause refers to row1, defined in table1. Hence the error.

Upvotes: 0

dush88c

Reputation: 2116

If you are going to ALTER Table column and immediate UPDATE the table including the new column in the same script. Make sure that use GO command to after line of code of alter table as below.

ALTER TABLE Location 
ADD TransitionType SMALLINT NULL
GO   

UPDATE Location SET TransitionType =  4

ALTER TABLE Location 
    ALTER COLUMN TransitionType SMALLINT NOT NULL

Upvotes: 11

Nick Reed

Reputation: 5059

I noted that, when executing joins, MSSQL will throw "Invalid Column Name" if the table you are joining on is not next to the table you are joining to. I tried specifying table1.row1 and table3.row3, but was still getting the error; it did not go away until I reordered the tables in the query. Apparently, the order of the tables in the statement matters.

+-------------+    +-------------+    +-------------+    
| table1      |    | table2      |    | table3      |    
+-------------+    +-------------+    +-------------+    
| row1 | col1 |    | row2 | col2 |    | row3 | col3 |    
+------+------+    +------+------+    +------+------+    
| ...  | ...  |    | ...  | ...  |    | ...  | ...  |    
+------+------+    +------+------+    +------+------+

SELECT * FROM table1, table2 LEFT JOIN table3 ON row1 = row3; --throws an error

SELECT * FROM table2, table1 LEFT JOIN table3 ON row1 = row3; --works as expected

Upvotes: 0

Khizer Amin

Reputation: 1

Refresh your tables.
Restart the SQL server.
Look out for the spelling mistakes in Query.

Upvotes: 0

Dreanaught

Reputation: 71

Following procedure helped me solve this issue but i don't know why.

Cut the code in question given by the lines in the message
Save the query (e.g. to file)
Paste the code to where it was before
Again save the query

Even if it seems to be the same query executing it did not throw this error

Upvotes: 1

Anderas

Reputation: 31

I just tried. If you execute the statement to generate your local table, the tool will accept that this column name exists. Just mark the table generation statement in your editor window and click execute.

Upvotes: 2

Molomby

Reputation: 6599

I was getting the same error when creating a view.

Imagine a select query that executes without issue:

select id
from products

Attempting to create a view from the same query would produce an error:

create view app.foobar as
select id
from products

Msg 207, Level 16, State 1, Procedure foobar, Line 2
Invalid column name 'id'.

For me it turned out to be a scoping issue; note the view is being created in a different schema. Specifying the schema of the products table solved the issue. Ie.. using dbo.products instead of just products.

Upvotes: 1

Chagbert

Reputation: 783

This error may ALSO occur in encapsulated SQL statements e.g.

DECLARE @tableName nvarchar(20) SET @tableName = 'GROC'

DECLARE @updtStmt nvarchar(4000)

SET @updtStmt = 'Update tbProductMaster_' +@tableName +' SET department_str = ' + @tableName exec sp_executesql @updtStmt

Only to discover that there are missing quotations to encapsulate the parameter "@tableName" further like the following:

SET @updtStmt = 'Update tbProductMaster_' +@tableName +' SET department_str = ''' + @tableName + ''' '

Thanks

Upvotes: 5

Ric

Reputation: 13248

Whenever this happens to me, I press Ctrl+Shift+R which refreshes intellisense, close the query window (save if necessary), then start a new session which usually works quite well.

Upvotes: 346