Before renaming a historian tag, decide whether only its name changes or whether the underlying measurement changes. For a true rename, preserve the measurement’s identity, establish how old and new historical paths resolve, and test every required consumer across the cutover. A working new live tag does not prove that earlier history remains accessible.
This is a historian engineer’s change-management task. The procedure below is a vendor-neutral planning and acceptance method, not a command to rewrite historian storage tables.
Decide whether this is the same measurement
A readable tag path may encode a line, equipment name or department that later changes. The process measurement can remain the same while that label changes. Conversely, reusing an old name for a different instrument location can create false continuity.
Record the old and proposed identifiers, source/provider, asset, measurement location, unit, data type, effective time and reason for change. Obtain the asset owner’s decision about continuity. Sensor replacement also needs a policy: replacing a sensor at the same measurement location may preserve a logical series while requiring a new instrument lineage; moving it to a different process point may require a separate series.
| Situation | Appropriate continuity decision |
|---|---|
| Folder renamed; same source and meaning | Preserve logical measurement identity and validate path resolution |
| Instrument replaced at the same approved measurement point | Preserve or split the logical series according to the site’s policy; retain instrument lineage |
| Old tag name reused for a different measurement | Keep the histories distinct, even if the text label matches |
| Meaning or effective date cannot be established | Hold automatic stitching and resolve the mapping exception |
The existing OPC UA identity and asset mapping article explains why source identifiers, asset keys and display labels have different roles. Historian renaming adds a separate obligation: queries and dependent applications must still reach the intended historical records.
Check the actual historian’s rename behavior
The Ignition rename discussion shows why this cannot be assumed. The poster wants history to remain active under a new name; replies describe direct SQL changes and warn about cached metadata. Treat those replies as evidence of the problem, not a supported migration recipe.
In the Ignition 8.1 database table reference, a historical configuration row can be retired and a new one inserted when a tag is renamed or otherwise changed. An older entry being retired does not, by itself, mean its stored measurements were deleted. Establish how the supported history query and browser expose them.
Ignition 8.3 documents updateRegisteredNodePath for Core Historian and Internal Historian only. That documented scope excludes SQL Historian. The function reports quality codes for success or failure; its existence does not establish that charts, external exports or other string references are automatically updated. Confirm the installed patch and provider before choosing a supported operation.
For another historian, inspect its own rename, alias or supported migration feature. If there is no supported operation that provides the required continuity, keep the old history addressable and implement a reviewed consumer mapping instead. A storage-table rewrite should not become a generic workaround.
Make the cutover queryable
Consider this fictional mapping for one unchanged pressure measurement. All times are UTC and the mapping uses an inclusive start and exclusive end.
| Logical measurement | Physical history path | Valid interval |
|---|---|---|
| M-P101-DP | AreaA/P101/Pressure | Before 12:00 |
| M-P101-DP | Utilities/P101/DischargePressure | From 12:00 |
Assume no provider-native alias joins the paths. A request for [11:50, 12:10) resolves the old path for [11:50, 12:00) and the new path for [12:00, 12:10). The consumer preserves each record’s original path and applies the logical identity separately. A record exactly at 12:00 belongs to the new interval under this example’s rule.
That rule is a design choice, not a historian default. Test the API’s endpoint behavior and adapt it. If both paths contain records at the cutover, compare them under an approved source-priority and duplicate policy. Do not silently choose by path name or arrival order. If the rename also changed scaling or timestamp assignment, the premise of an unchanged measurement needs to be revisited.
An alias or mapping can join logical access; it does not repair missing records or prove that two streams measure the same physical quantity.
Test consumers before retiring the old reference
Inventory the consumers that use a literal path: trends, reports, calculations, scheduled exports and external integrations. A historian’s rename feature may operate at a different boundary from those references. Where TDengine IDMP is a consumer, include its metric attribute references in that inventory.
Save a small pre-change query and its parameters. In an approved test or maintenance procedure, apply the supported change, then check a window entirely before the cutover, one entirely after it, and one crossing it. Compare source identity, values, quality, timestamp precision and expected boundary records. Test both the engineering query and the actual report or chart; one can succeed while the other still uses the obsolete path.
Also check a late historical record or correction under the old identifier if that behavior is required. Establish whether its routing follows event time, current configuration or another provider rule. If it cannot be handled, record the limitation before signing off continuity.
Keep the old reference available until the required consumers pass and the owner accepts the exception list. Retain the mapping version, effective time, supported change result and recovery plan. A completed rename should leave another engineer able to explain both how the tag is called today and how yesterday’s history is retrieved.


