Enabling and Disabling a Versioned Repository - Teradata Meta Data Services

Teradata Meta Data Services User Guide

Product
Teradata Meta Data Services
Release Number
15.00
Language
English (United States)
Last Update
2018-09-27
Product Category
Teradata Tools and Utilities

Enabling and Disabling a Versioned Repository

A versioned repository can be created with either the metacreate or metamigrate command‑line tool.

To enable versioning for a repository:

1 Do one of the following:

To create a new repository with versioning enabled:

✔ Select Start > All Programs > Teradata Meta Data Services > Create MDS Repository > Create with versioning.

To enable versioning for an existing repository:

✔ Select Start > All Programs > Teradata Meta Data Services > Migrate MDS Repository > Migrate with versioning.

2 Follow the on-screen prompts.

The metamigrate tool can be run at any time on an Teradata MDS repository to enable or disable versioning. This provides the flexibility to experiment with a versioned repository at any time, not just when the repository is created or migrated from a previous release of Teradata MDS.

To disable versioning for a repository:

1 Select Start > All Programs > Teradata Meta Data Services > Migrate MDS Repository > Migrate without versioning.

2 Follow the on-screen prompts.

All of the frozen, non-modifiable versions for all data objects in the repository will be deleted, and all of the AIMs and classes in the repository will be marked as not supporting versioning.

Versioning Data in Specific Metamodels or Classes

By default, when versioning is enabled in a repository, metadata classes from all metamodels will support versioning of data except for objects from the reserved AIM MDSMetamodel. MDS Repository Explorer, however, provides the ability to disable or enable versioning of data for any particular metamodel or just one or more of its metadata classes for those cases where versioned information is only needed for a subset of the metadata in the repository.