Using TSQL Variables: Subtle BUG when assigning values to Variables via a Query

re: Using TSQL Variables: Subtle BUG when assigning values to Variables via a Query

Chris — Mon, 31 Aug 2009 18:09:04 GMT

I make sure to reset my variables to NULL when I am going to use SELECT to set a variable or I just use SET. This has been true since at least SQL Server 2000.

re: Using TSQL Variables: Subtle BUG when assigning values to Variables via a Query

ALOJ — Mon, 31 Aug 2009 05:55:55 GMT

IE 7 shows javascript error and does not post comments to this blog. FF works though.

re: Using TSQL Variables: Subtle BUG when assigning values to Variables via a Query

ALOJ — Mon, 31 Aug 2009 05:54:10 GMT

There is some related discussion here:

http://www.sqlservercentral.com/Forums/Topic708753-338-1.aspx

One more options .. you could use statement like this

set @x = (select 1 where 2=3)

to be sure that you get NULL back when there will be nothing returned by "SELECT"

One benefit of the above is ..that it will crash if "select" return more than 1 row .. vs. quietly fetching the first row in the resultset