SQL Error (137): Must declare the scalar variable from HeidiSQL

Asked Feb 04 '16 at 09:01

Active Oct 27 '16 at 05:01

Viewed 1,574 times

I don't really see where I'm going wrong with this fairly simple query:

DECLARE @id int;
SET @id = 84;

INSERT INTO Activity_Ax_Account_Numbers
VALUES(@id,'N/A');

INSERT INTO Activity_Files
VALUES(@id,0x66696C6C65722073747566660D0A,'Filler',0);

INSERT INTO Activity_Settings
VALUES(@id,0,0,0);

I have to do the above a couple of times as I need to transfer data from an old database to a new one by hand (Don't ask, that's just how it is T_T). So the above is something I'm going to do a lot and instead of doing this by hand I thought I could just make a simple query I could run as then I only have to do one row of data by hand for every entry instead of four.

But I get the error in the title when I try to execute the query. It's an MS SQL 11.0 server that I connect to via HeidiSQL.

edited Feb 04 '16 at 10:54

TT.

15,774
6
47
88

asked Feb 04 '16 at 09:01

OmniOwl

5,477
17
67
116

Is 66696C6C65722073747566660D0A supposed to be a varchar? – Marko Juvančič Feb 04 '16 at 09:05
`INSERT INTO Activity_Files VALUES(@id,'66696C6C65722073747566660D0A','Filler',0);` – Rahul Tripathi Feb 04 '16 at 09:08
@RahulTripathi it's not a varchar it's a varbinary. But even then I still get the same error if I do the above. – OmniOwl Feb 04 '16 at 09:10
Relying on implicit order of column names in an INSERT statement is a big mistake. Always supply the column names in an INSERT statement: Write `INSERT INTO (, ..., ) VALUES (, ..., );`. – TT. Feb 04 '16 at 09:52
Do any triggers or similar exists on the tables? Might be the error message is from something else happening when you run your query? – Allan S. Hansen Feb 04 '16 at 10:01
@AllanS.Hansen No there are no triggers at all. – OmniOwl Feb 04 '16 at 10:22
Which of the above statements throws the error? – Allan S. Hansen Feb 04 '16 at 10:25
The first "Values" statement. – OmniOwl Feb 04 '16 at 10:26
Are you running the whole batch, or just selecting that first statement and pressing ctrl-E to run it separately from SSMS? – TT. Feb 04 '16 at 10:44
It appears that HeidiSQL might just not be able to deal with that syntax. – OmniOwl Feb 04 '16 at 10:53
Look [here](http://stackoverflow.com/questions/8567222/how-to-update-a-varbinary-field-with-a-specific-value). `Salt=CAST('bPftidzyAQik' AS VARBINARY),` – Bogdan Bogdanov Feb 04 '16 at 11:00

SQL Error (137): Must declare the scalar variable from HeidiSQL

0 Answers0