Timeline for Why does my query end up with two seeks instead of one and how do I fix that?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2014 at 21:46 | comment | added | Rob Farley | Using the time field in an expression that will be nulled out by a null (either being returned that way or by the LJ) won't be helping either. I think SQL is trying to differentiate between the two types of null, but can't be sure. | |
| Aug 27, 2014 at 21:36 | comment | added | usr | This is a likely fix. But why did SQL Server add the two seeks? Shouldn't a single backwards scan be enough to find both not-null as well as null values? | |
| Aug 27, 2014 at 20:33 | history | answered | Rob Farley | CC BY-SA 3.0 |