When you get into querying Computer Properties at scale, there are several things that can impact you:
- When querying for a plural property value, any computer missing a result will “fall out” of the entire query result
- When querying for a singular property value, any computer missing a result will throw an error and abort the entire query.
- When looking up multiple properties on multiple computers, performance can decrease dramatically depending upon how the query is formed, especially if “each computer” triggers a lookup of “every property”, based on how the clauses are formed.
The go-to reference on handling all of these cases is the posting from @brolly33 at Efficient Session Relevance Query for Computer Properties which lays out all of these cases and gives a template for querying multiple computer properties at large scale.