https://lobsterpot.com.au/blog/2012/01/10/apply-not-exactly-set-based/ Mon, 16 Jan 2012 02:57:43 +0000 hourly 1 https://wordpress.org/?v=6.9.4 https://lobsterpot.com.au/blog/2012/01/10/apply-not-exactly-set-based/#comment-2069 Mon, 16 Jan 2012 02:57:43 +0000 http://blogs.lobsterpot.com.au/?p=3070#comment-2069 Would another solution be chaining multiple CTEs together?

]]> https://lobsterpot.com.au/blog/2012/01/10/apply-not-exactly-set-based/#comment-2068 Mon, 16 Jan 2012 01:46:43 +0000 http://blogs.lobsterpot.com.au/?p=3070#comment-2068 Simple enough, – APPLY is not a statement of the ISO ANSI SQL language standard. What’s not standard  better not be used.

]]> https://lobsterpot.com.au/blog/2012/01/10/apply-not-exactly-set-based/#comment-2067 Sun, 15 Jan 2012 03:26:40 +0000 http://blogs.lobsterpot.com.au/?p=3070#comment-2067 Haha, yeah. I’m pretty sure a few months ago I refactored a statement using an APPLY/RANK combination and found out the same thing as you at the end 🙂 Many a keyboard thumping was had that day!

]]> https://lobsterpot.com.au/blog/2012/01/10/apply-not-exactly-set-based/#comment-2066 Tue, 10 Jan 2012 16:24:54 +0000 http://blogs.lobsterpot.com.au/?p=3070#comment-2066 Hey, thanks for picking up my topic again! This is all really fantastic stuff you’ve been sharing about APPLY.

]]>