A co-worker and I were playing with some temporal sets and we noticed a bit of strange behaviour when working with the criteria definition of <attr> is prior to “today”.
Simply put, the value of Today that is used in the criteria is Now. If your datetime value is prior to now versus today, it will be a enumerated as a member of the set. The granularity of the event seems to be limited down to the second for the testing we did however, I doubt that neither Bob or I am capable of discerning, let alone testing to the millisecond.
This is illustrated in the examples below using October 27th as “today” and the current time being 2:52:30 PM. (The last 3 columns are relative to “Today”)
|User Attribute||Prior to||Equal to||After|
|October 27th 1:00 AM||True||False||False|
|October 27th 2:52:29 PM||True||False||False|
|October 27th 2:52:30 PM||False||True||False|
|October 27th 2:52:31 PM||False||False||True|
|October 27th 5:00 PM||False||False||True|
Note that the actual criteria do not allow you to use an “equal to” setting and I had always found that peculiar but now I have a better understanding as to why that is.
Remember, that temporal groups will not recalculate the memberships until either the SQL Agent Job runs at 1:00 am or there is some other change in the actual attribute values themselves making up the criteria of the group/set.