I learned long ago that this is problematic, but can't remember why.
I learned long ago that this is problematic, but can't remember why.
An AFAttribute that does not have a data reference is a static (or constant) value that is not meant to be historized or changed. An analysis writing values to an AFAttribute is attempting to historize values. Since the output is a static attribute, the timestamps are ignored and only the time context of the AFElement is used for that static value - typically that is Jan 1, 1970. The many values will not be written to a PI Point but rather somewhere inside the SQL Server PIFD. It will repeatedly write the calculated values which goofs up the indexing, audit tables, the transaction log, and degrades the SQL Server.
It is VERY problematic. Do NOT do it. You are only inviting trouble.
A more detailed related issue if found at:
KB01398
FindChanges_AT Table May Cause PI AF Server Performance Issues