Invalid column name error when trying to delete a row in SQL server

Question

0.00/5 (No votes)

See more:

Getting error in SQL Server when i am trying to delete a row. the column which it is complaining already exists...

DELETE
from [dbo].[sample]
WHERE [pk_sample] = '642388'

(1 row affected)

(1 row affected)

(1 row affected)

(1 row affected)
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'SampleCondition'.

What I have tried:

I have tried checking the column if it exists and what value it has.. it has a Null value passed into it...

Posted 8-Mar-19 23:55pm

Member 3749400

Updated 9-Mar-19 0:44am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2019-03-09T00:44:00

I'd start by looking at the code you are using to execute that SQL, and any TRIGGERS you have set in the DB: the number of messages you have would indicate that you are doing it in a loop or similar, and it's probably the code around that SQL that is causing the problem - just issuing that command as it stands will give you one single "N rows affected" unless you have a TRIGGER on the delete which is trying to do a load of other things and that TRIGGER code has a problem.