Interim vs. Final Archive Sets

Intended Audience: Developers, DBA’s and Administrators of Stat ACM

Intended Subject: Knowing the Who, What, When, Where and Why of Interim vs. Final Archive Set Creation.

Intended Reaction: Happy Stat Customers, Happy Stat Users

Keywords: Stat Archive Set, Final Archive Set, Interim Archive Set, Approvals, Workflow, Migration.

Hello fellow Stat Developers and Migrators,

As a Solutions Architect it is my job to demonstrate the value of a product like Stat. I’ve worked with this product since 2004 and what I enjoy most is that I’m still learning…

One of the things I do is work with your Account Manager doing what we call a Customer Care Session.

During these Customer Care Sessions I am often asked recurring questions on Archive Set creation, such as:

… When is the correct time to create an Interim Archive Set vs. a Final Archive Set?

… Who should be creating them?

… Where should they be created? In Development, or based on the code approved in the Test environment?

The Definition Please!

"I like good strong words that mean something."- Louisa May Alcott, Little Women

Let’s take a look at the glossary in the Stat Administrator’s Guide and see what it says about Archive Sets.

Archive Set:

A snapshot of a set of objects that have been grouped together for archiving purposes. There are three types of archive sets: Base, Interim, and Final.

Interim Archive Set:

An interim snapshot of objects while they are in the process of being modified. An unlimited number of interim archive sets can be created. Interims should be created from the environments in which objects were modified which would probably be Development. Interim archive sets should be migrated to one or many target environments for testing and evaluation.

Final Archive Set:

The final snapshot of all objects taken from the Development environment. The final archive set should be created after all changes have been approved. The final archive set should be migrated to all environments on the migration path so they are all in sync. Only one final archive set exists per CSR.

Key differentiators of Final Archive Sets:

…Should be taken from Development.

…Should be taken after approvals are completed.

…Should be migrated to all environments on the path.

…Should be only one “Final” Archive Set per CSR.

Given the above points, the scenario for Final Archive Sets should be similar to the following:

1. Check out the code/project to create the Base Archive Set from the base environment.

2. Modify the code as needed and create Interim Archive Sets.

3. Migrate the Interim Archive Sets to Test and other target environments.

4. Once tested successfully, request approvals for the code to progress.

5. After the code has been approved in the Test environment, either create the Final Archive Set from Test or return to Development and create the Final Archive Set*.

6. The workflow should then be promoted and additional approvals should be required before continuing the migration process.


* When a Final Archive Set is created Stat adds all objects in the CSR to the Final Archive Set automatically. Once created, objects cannot be added or removed from a Final Archive Set.

Additional Tips on Final Archive Sets:

- Final Archive Sets are not mandatory although they are strongly recommended.

- The use of Final Archive Sets simplify migrations to higher environments. There should be no confusion since there can only be one Final Archive Set per CSR.

- A Final Archive Set is just that – Final. Once created, users cannot add or remove objects from it.

- A Final Archive Set can be created from any environment along the migration path of the particular CSR.

Thanks for taking the time to read this blog and I hope you found it informative, because after all…

"So difficult it is to show the various meanings and imperfections of words when we have nothing else but words to do it with."
- John Locke


William R. Hart

Solutions Architect

Dell | Quest Group, Pre-Sales