NULL values handled differently in stored procedure
From: Mike (anonymous_at_discussions.microsoft.com)
Date: 10/04/04
- Next message: Paul S Randal [MS]: "Re: Sysindex table problems"
- Previous message: Steve Thompson: "Re: SQL Sever loses Shares"
- Next in thread: David Portas: "Re: NULL values handled differently in stored procedure"
- Reply: David Portas: "Re: NULL values handled differently in stored procedure"
- Reply: Maury Markowitz: "RE: NULL values handled differently in stored procedure"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 4 Oct 2004 12:26:35 -0700
Can someone explain why the following is happening:
SELECT EventId, MDResponse FROM tblEvent
WHERE (MDResponse NOT IN(1, 3))
ORDER BY MDResponse
If I run the above statement in Query Analyzer it returns
all rows where MDResponse is not 1 or 3. No NULL
MDResponse rows are returned. This is what I expected.
If I run it as a stored procedure it also returns the
NULL valued rows.
Why the difference?
Thanks
Mike
- Next message: Paul S Randal [MS]: "Re: Sysindex table problems"
- Previous message: Steve Thompson: "Re: SQL Sever loses Shares"
- Next in thread: David Portas: "Re: NULL values handled differently in stored procedure"
- Reply: David Portas: "Re: NULL values handled differently in stored procedure"
- Reply: Maury Markowitz: "RE: NULL values handled differently in stored procedure"
- Messages sorted by: [ date ] [ thread ]