Re: IS NULL not working in WHERE clause.
From: Earl Newcomer (EarlNewcomer_at_discussions.microsoft.com)
Date: 12/20/04
- Next message: Andrew Pasetti: "RE: Sql order by question"
- Previous message: Questar: "ORDER BY and IDENTITY"
- In reply to: David Portas: "Re: IS NULL not working in WHERE clause."
- Next in thread: Aaron [SQL Server MVP]: "Re: IS NULL not working in WHERE clause."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 20 Dec 2004 09:25:05 -0800
David,
Steve Kass had an interesting suggestion to use the option (maxdop 1). This
removed the parallelism operation from both the top and bottom branches of
the execution plan and caused the failing query to return only those rows
with a time_id of null.
Do you know why a parallelism operation in the query execution would return
all rows instead of using the constraint of where time_id is null?
Thanks,
Earl
"David Portas" wrote:
> If the problem isn't reproducable then you're potentially looking at corrupt
> data. Try DBCC CHECKDB. If that doesn't get you anywhere then open a case
> with product support.
>
> --
> David Portas
> SQL Server MVP
> --
>
>
>
- Next message: Andrew Pasetti: "RE: Sql order by question"
- Previous message: Questar: "ORDER BY and IDENTITY"
- In reply to: David Portas: "Re: IS NULL not working in WHERE clause."
- Next in thread: Aaron [SQL Server MVP]: "Re: IS NULL not working in WHERE clause."
- Messages sorted by: [ date ] [ thread ]
