I was working on a problem and I was desperate to do a clean job and not create a mess that no one can maintain it, and accidentally I read an article about SQL Apply operator.
The APPLY operator allows you to invoke a table-valued function for each row returned by an outer table expression of a query.
The table-valued function acts as the right input and the outer table expression acts as the left input. The advantage over inner join is that it is faster and you can handle conditional joins easily using this trick.\r\nA quick reminder on the terms.
\n\n\nINNER JOIN is the most used construct in SQL: it joins two tables together, selecting only those row combinations for which a JOIN condition is true.
\n
SELECT *\r\nFROM tblUser\r\nJOIN tblProfile\r\nON tblUser.Id = tblProfile.UserIdBut for some tasks the sets are not self-sufficient. For instance, let’s consider the following query:\r\nWe have tblUser and tblProfile. tblProfile has a column called rowcount.
For each row from tblUser we need to select first rowcount rows from tblProfile, ordered by tblProfile.Id.
We cannot come up with a join condition here. The join condition, should it exist, would involve the row number, which is not present in tblProfile, and there is no way to calculate a row number only from the values of columns of any given row in tblProfile.
That’s where the CROSS APPLY can be used:
SELECT _\r\nFROM tblUser\r\nCROSS APPLY\r\n(\r\nSELECT TOP (tblUser.rowcount)\r\nFROM tblProfile\r\nORDER BY\r\nId\r\n) t2Summary:
\nWhile most queries which employ CROSS APPLY can be rewritten using an INNER JOIN, CROSS APPLY can yield better execution plan and better performance, since it can limit the set being joined yet before the join occurs.