mpi_segattr settings
Settings in the mpi_segattr table control how updated values for an attribute are assigned an active status (nsActive) and how many updated values are stored in history (nsExist).
If nsActive is set to 0, an indefinite number of values are retained with an active status. A setting of 1 means that only one attribute value of a type can have an active status, a value of 2 maintains two active values, and so on. Any updates to that value results in setting the new value to active and the previous value becomes inactive. Whatever number nsExists is set to, the MDM operational server stores that number of values, regardless of status, in history. For example, if nsExists is set to 2 and there are two attribute values stored, a third value causes the earliest value to be removed (trimmed) from the MDM database.
The following table shows the concept of nsActive and nsExists without the outcome being affected by the mode type. This example is just for illustration purposes, because the member mode always influences the way attributes are stored. In this example, nsActive is set to 2 and nsExists is set to 3.
Date of attribute creation and change | Attribute in MDM database | Status |
---|---|---|
2012-01-10 | PHONE = 6024459797 | A (active) |
2012-02-24 | PHONE = 6025556789 PHONE = 6024459797 |
A (active) A (active) |
2012-04-03 | PHONE = 4805553232 PHONE = 6025556789 PHONE = 6024459797 |
A (active) A (active) I (inactive) |
2012-10-10 | PHONE = 4805556060 PHONE = 4805553232 PHONE = 6025556789 PHONE = 6024459797 |
A (active) A (active) I (inactive) Trimmed from database |