Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference

Repository Guide

Repository Guide

Purging Versions of Objects

Purging Versions of Objects

You can purge specific versions of objects, or you can purge all versions of objects.
To permanently remove an object version from the repository, you must purge it. You need to check in object versions to purge them. You might want to purge a version if you no longer need it and you want to reduce the size of the repository database.
You can purge multiple versions of an object from the repository at the same time. To completely purge an object from the repository, you must purge all versions. If you purge a version that is not the latest version, the repository keeps a record of the purge in the object history. If you purge the latest version, the repository does not keep a record of the purge.
You can revert to an older version of an object by purging more recent versions. You cannot, however, promote an older version to the current version without purging the more recent versions. For example, you create 12 versions of a mapping. You then determine that you need to use version 10 of the mapping instead of version 12. You can purge versions 11 and 12 to make version 10 the current version.
You use the Repository Manager to purge versions. When you purge versions of objects, you can perform the following tasks:
  • Purge individual object versions.
    You can select object versions in the View History window or Query Results window to purge the individual object versions.
  • Purge versions based on criteria.
    You can purge versions at the repository, folder, or object level based on purge criteria. This type of purge is called an advanced purge. Use advanced purges to purge deleted or active objects. For deleted objects, you can specify the objects to purge based on the date of deletion. For active objects, you specify the versions to purge based on the version number, the check-in date, or both.
  • Preview purge results.
    Preview an advanced purge to view the purge results before you purge objects from the repository. You can view summary or detailed information about the purge.
  • Purge composite objects.
    You can purge versions of composite objects, and you can purge versions of dependent objects that make up composite objects. View object dependencies before you purge composite objects. You might get unexpected results if you do not determine the dependent object versions that a purge affects.
The following table shows the Repository Manager commands that you can use to purge versions at the object, folder, or repository level:
Purge Type
Single Object Version
Multiple Object Versions
Versions at Folder Level
Versions at Repository Level
By Object Version
(View History Window)
yes
yes
no
no
By Object Version
(Query Results Window)
yes
yes
no
no
Based on Criteria
(Navigator)
yes
yes
yes
yes
Based on Criteria
(View History Window)
yes
yes
no
no
Based on Criteria
(Query Results window)
yes
yes
no
no

0 COMMENTS

We’d like to hear from you!