问题
This is my simplified statement
SELECT ...
FROM tab1 AS i FULL OUTER JOIN tab2 AS d ON i.[Id]=d.[Id]
WHERE d.[Data]<>i.[Data] OR
(d.[Data] IS NULL AND i.[Data] IS NOT NULL) OR
(d.[Data] IS NOT NULL AND i.[Data] IS NULL)
I want to get all entries that are
- i.[Data] is different from d.[Data]
- At least one value in table i or d is NOT NULL
So I don't want to see records were and i and d contain the same data or are both NULL.
My statement look so long and complicated. Is there an easier way?
Using ISNULL(d.[Data],'')<>ISNULL(i.[Data],'')
works for text, but not for DATE
or TIME(0)
columns.
My statement works for every type.
回答1:
You can simplify to:
SELECT ...
FROM ...
WHERE d.[Data] <> i.[Data]
OR IIF(d.[Data] IS NULL, 0, 1) = IIF(i.[Data] IS NULL, 1, 0)
See live demo.
回答2:
Yes you can, and you can get the optimizer to recognize it too.
Paul White has this little ditty:
WHERE NOT EXISTS (
SELECT d.[Data]
INTERSECT
SELECT i.[Data])
This works because of the semantics of INTERSECT
which deal with nulls. What this says is "are there no rows in the subquery made up of value B and value B", this will only be satisfied if they are different values or one is null and the other not. If both are nulls, there will be a row with a null.
If you check the XML query plan (not the graphical one in SSMS), you will see that the operator it uses will have CompareOp="IS"
and not EQ
.
See the full plan here.
The relevant part of the plan is:
<Predicate>
<ScalarOperator ScalarString="@t1.[i] as [t1].[i] = @t2.[i] as [t2].[i]">
<Compare CompareOp="IS">
<ScalarOperator>
<Identifier>
<ColumnReference Table="@t1" Alias="[t1]" Column="i" />
</Identifier>
</ScalarOperator>
<ScalarOperator>
<Identifier>
<ColumnReference Table="@t2" Alias="[t2]" Column="i" />
</Identifier>
</ScalarOperator>
</Compare>
</ScalarOperator>
</Predicate>
I find the optimizer works very well this way round, rather than doing EXISTS / EXCEPT
.
I urge you to vote for the Azure Feedback to implement a proper operator
来源:https://stackoverflow.com/questions/66138082/is-there-a-way-to-simplify-a-null-compare-of-2-values