A Unified Namespace Determines Your Historian Schema, Not the Other Way Around (opens in new tab)

Most teams design the historian first and connect it to a Unified Namespace later. This article argues the reverse: the UNS owns identity, so it should dictate the historian schema. That means storing tag identity in a relational namespace table with surrogate keys and keeping history in a narrow hypertable. The result: tag renames, hierarchy changes, and churn happen without rewriting history.