must declare the scalar variable!

Question

must declare the scalar variable!

edalatfeizi

Old Hand

Points: 300
More actions
May 9, 2013 at 1:45 am

#293762

hello every body.
I have a question about declaring variable in sql server 2012.
when i declare a variable for example :
DECLARE @X INT;
when i compile this line it's true
but when i set a value in different line to this variable:
SET @X =12;
it returns an error message as:
Must declare the scalar variable @X
how can i fix it?

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 1

Can you post all of the code between the DECLARE and the SET?

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

edalatfeizi Old Hand Points: 300 More actions · Answer 2

thank you ChrisM@Work.

but I have not entered any code between DECLARE and SET my code is:

DECLARE @X INT;

SET @X =12;

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 3

edalatfeizi (5/9/2013)
thank you ChrisM@Work.
but I have not entered any code between DECLARE and SET my code is:
DECLARE @X INT;
SET @X =12;

Not even this?

DECLARE @X INT;

GO

SET @X =12;

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

edalatfeizi Old Hand Points: 300 More actions · Answer 4

edalatfeizi

Old Hand

Points: 300

May 9, 2013 at 2:10 am

#1613637

no it's just

DECLARE @X INT;

SET @X =12;

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 5

edalatfeizi (5/9/2013)
no it's just
DECLARE @X INT;
SET @X =12;

What are you using as your client?

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

John Mitchell-245523 SSC Guru Points: 148809 More actions · Answer 6

You need to run the two statements as one batch, since a variable will only "live" until the end of the batch.

John

Grant Fritchey SSC Guru Points: 398909 More actions · Answer 7

You sure there's not something else at work here? I just tested your code and it's working fine. There's no intervening code of any kind?

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

OTF SSCertifiable Points: 6104 More actions · Answer 8

Your code run as a batch should work.

I think what you are probably doing is highlighting and running the statements individually which would reproduce the error you are getting.