mattpayne59
asked on
Strange SQL Update Issue
I am trying to run a simple update statement on a database. Here is the update:
UPDATE dbo.TkprBudget
SET tkprbudget.TBBudHrsWrk = '2'
WHERE tbemp = '130' and tbprdyear = '2015' and TBPrdNbr = '1'
When I run it I get these errors:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '+'.
Msg 208, Level 16, State 0, Line 1
Invalid object name '##XML'.
I have no clue what this is talking about. There is no + sign and I dont know what object ##XML is referring to either. Am I missing something obvious here? This is SQL 2012. Thank you for your help.
UPDATE dbo.TkprBudget
SET tkprbudget.TBBudHrsWrk = '2'
WHERE tbemp = '130' and tbprdyear = '2015' and TBPrdNbr = '1'
When I run it I get these errors:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '+'.
Msg 208, Level 16, State 0, Line 1
Invalid object name '##XML'.
I have no clue what this is talking about. There is no + sign and I dont know what object ##XML is referring to either. Am I missing something obvious here? This is SQL 2012. Thank you for your help.
ASKER
Sorry... Not sure how access got in there as a topic. This is straight sql.
I am just running the query in the query window in SQL management studio.
I am just running the query in the query window in SQL management studio.
Running [ only & just the displayed query ] in the query window in SQL management studio
I have no idea, sorry.
I have no idea, sorry.
Check if in that query window exists more code. If so, select only the statement that you want to run and press F5 or Execute button.
ASKER
It only has that code. I commented out the rest. I also connected using a 2008 management studio and copied that code in only to the query and I got the same issue. It is very strange.
Then check if the TkprBudget has any update trigger.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I see the statement being executed in Profiler but I dont see anything else executing around it. No stored procedures or triggers.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Definitely some triggers... I dont think this is going to be possible with a simple update query then. I will go another route. Thank you for the help everyone.
You can always code a "bypass" in the trigger(s), to have it(them) exit without doing anything when you explicitly tell the trigger not to. CONTEXT_INFO is the easiest way to do that.
How are you running the update query?