What This Field Means
The permanent record number used to keep this unit separate from every other unit in the guide.
This is the stable internal handle for one canonical unit record. Names, locations, commands, and status can change, but the Unit ID lets the site keep those facts attached to the same record and lets one unit point unambiguously to another.
How to Read It Correctly
It is not a Unit Identification Code, hull number, squadron number, office symbol, or any identifier issued by a military service. A visitor normally uses the unit name, aliases, dates, and relationships to find a record; the site uses Unit ID to keep the result technically exact.
Example
Unit ID 44053 identifies one canonical unit record; it is not a UIC, hull number, or designation.
Technical Specification
The database column is [USMIL-Unit].[Unit].[UnitID]. The table’s primary identity key. It identifies one canonical Unit row and is the target of parent, predecessor, and successor references.
The database creates this integer automatically. It must be unique, cannot be blank, and must never be recycled or edited to resemble an external military identifier.
| Property | Definition or current value |
|---|---|
| Database column | UnitID |
| Column order | 1 |
| SQL data type | bigint |
| Kind of information | System-generated primary identifier |
| Cardinality | One stored value per Unit row. |
| Required | Yes |
| Database default | No database default |
| Key or relationship | Primary key for the Unit table |
| Database check constraint | ([CurrentStatus]=N'Planned' OR [CurrentStatus]=N'Status unknown' OR [CurrentStatus]=N'Historical' OR [CurrentStatus]=N'Inactive' OR [CurrentStatus]=N'Current') |
| Live population | 9341 of 9341 Unit records (100%) |
| Distinct nonblank values in the live table | 9341 |
| Live profile measured | September 2, 2026, 20:43 UTC |
Allowed Values and Definitions
No preset menu applies to this field. It stores an identifier, relationship, measurement, date, timestamp, or evidence-derived narrative. Valid content is governed by the SQL type, key relationship, nullability, retained evidence, and the field-specific recording rule above. A list of observed contents would be data, not a list of allowed options.
Missing, Unknown, and Conflicting Information
This column cannot be NULL in the Unit table. When the underlying fact is incomplete, the record must use an allowed explicit disposition or a supported evidence-derived statement. Required storage does not mean that every historical fact is known, and it never authorizes a guessed value.
Connections to Other Fields
- Entity ID — The connection between the unit record and the broader record for the same real-world organization.
- Official Unit Designation — The unit’s full official name or designation as supported by military records.
- Parent Unit — The immediate higher organization under which the unit is placed in this record.
- Predecessor Unit — The earlier unit identity officially connected to this unit’s lineage.
- Successor Unit — The later unit identity officially connected to this unit through succession, redesignation, consolidation, or another supported lineage event.