Home > Archive > MS SQL Server > June 2005 > Very strange problem: is null doesn't work when using multiple CPU









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Very strange problem: is null doesn't work when using multiple CPU
James Ma

2005-06-30, 1:23 pm

Hi,

This is a simple SQL:
select orders_id,keycode,va
lidpayment,moneyrece
ived,prospect_id
from orders
where Keycode='ABCDEF123' and validpayment='valid'
and moneyreceived>0 and
prospect_id is NULL
option (maxdop 1)

If I run with option (maxdop 1), it returns correct lines. But if I run
without that option, it returns all those lines even including prospect_id is
not null. That is incorrect. I used DBCC CHECKTABLE and found nothing wrong.
What can cause this strange problem?

Can anyone here shed some light on this?

Thanks in advance.
James

David Gugick

2005-06-30, 8:23 pm

Please don't multi-post. Cross-post to multiple groups when necessary.
Answered in "programming".

--
David Gugick
Quest Software
www.imceda.com
www.quest.com

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com