A Bit of Background
Several years ago, during a client's web app rebuild/refresh, I decided to clean up some of the gnarly baggage behind their reporting mechanism.
In the interest of hopefully saving Future Me some time, I'm writing this little bit so as not to have to stumble to remember a simple premise:
How do I LEFT JOIN the same table more than once in a query?
For as many times as I've had to join a table more than once (effectively as a certain type of generic lookup table), you'd think I'd have this memorized. But I always get caught forgetting to proper alias both joins.
As I wrote about two weeks ago (while in mid-run), we just had our early summer theatre production. It was, in my opinion, a very successful run...though bittersweet to see it end after two weekends (and six shows). We had a great and consistent audience, which speaks well to the attempt at doing a show over two weekends in June. Our next board meeting will reveal the "final" financial result of our activities.
One of the things I've baked into our production task sequence for "multi-user devices" is a secondary way to automatically determine a device's use case while in the WinPE stage. The primary, preferred way to determine use case is by the use of SCCM collection variables, but those require a known object (in the proper collection) to function as designed. Thus, for all rebuilds of known devices, the use case is figured out by collection variable.