What Versioning Does
In a versioned repository, whenever an application changes something about an existing object in the repository, Teradata MDS will freeze the current property values of the object, create a new copy of the object, called a new version, and then connect the new copy to the previous version. The new property values passed by the application will be set in the new version, and the new version will be the one seen by any application. Once a new version of an object has been created, the previous versions that retain the historical values can never be modified.
The versioning capability can only be applied to data objects in a class. The definitions of Application Information Metamodels (AIM), classes, relationships, properties, users, application groups, and security profiles can’t be versioned.
When versioning is enabled for the Teradata MDS repository, it will automatically apply to any existing metamodels and classes in the repository, and it will automatically be applied to any new metamodels and classes subsequently added to the repository. An Administrator can limit which of the existing AIMs and classes should retain historical information.