Timeline for Specifying columns in LEFT JOIN through subquery beneficial performance wise?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2014 at 10:39 | answer | added | Peter Henell | timeline score: 4 | |
| Feb 19, 2014 at 15:32 | comment | added | Apeiron | Forgot to add it to the example (might have as well removed the TOP altogether). Updated. | |
| Feb 19, 2014 at 15:30 | history | edited | Apeiron | CC BY-SA 3.0 |
added 34 characters in body
|
| Feb 19, 2014 at 14:24 | comment | added | Aaron Bertrand | What do you think TOP even means, without ORDER BY? | |
| Feb 19, 2014 at 14:04 | comment | added | Peter Henell | Look at the query plan for both queries. Especially look at the "Output List" of any Scan or Seek operators. They will show you which columns that will be part of the next steps in the processing of the query. It is likely that it will use the same plan for both queries in this case and in most similar cases. | |
| Feb 19, 2014 at 13:40 | history | tweeted | twitter.com/#!/StackDBAs/status/436133143465459712 | ||
| Feb 19, 2014 at 12:56 | history | edited | Thomas Stringer |
edited tags
|
|
| Feb 19, 2014 at 12:44 | history | edited | Apeiron | CC BY-SA 3.0 |
added 229 characters in body
|
| Feb 19, 2014 at 12:38 | history | asked | Apeiron | CC BY-SA 3.0 |