ArcPlus
The ArcPlus provide an easy to implement Data Archive and Restore solution for all products based on relational database. In this solution, the data from a source database is archived to a target database with referential integrity intact. The Archived Data can be restored to its original or different source.
An Archive solution consists of an Archive Definition, build using ArcPlus. An Archive Definition consists of a Data Model and Business Rules. A Data Model is the parent child relationship between tables. The Business Rules are the selection criteria to select the data to Archive from the source database.
Product Features
- Archive data with referential integrity intact.
- Restore partial or complete data.
- Archive a single table or a complete set of tables based on relation.
- Archive data in one or two step method. In two step method, the copy and delete process is performed as two separate processes. In two step method, the copied data can be verified before it is deleted from the source.
- Archived data is stored in the similar set of tables as source tables. The Archive tables may contain additional or less columns than the source tables.
- Supports Object Mapping that enables storing archived data in a separate "archive" set of tables within the source database.
- Ability to provide Archive keys in an external source. For example, a set of Purchase Order Number that should be archived can be provided in an external source (table or flat file).
- Ability to update column(s) within source table to indicate that the corresponding data is archived.
- Ability to collect statistics on tables affected by Archiving Process.
- Archived data in stored in a non-proprietary format.
- Migrate data from one database type to another database type. For example, DB2 to Oracle, Oracle to MS/Sql Server, DB2 to MS/Sql Server, etc.
Additional Features
The ArcPlus can also be used to Copy, Delete, Purge, or Cleanup data from the source database.
- In Copy process, the data from the source database is copied to target database based on Data Model and Business Rules.
- In Delete process, the data from the source database in deleted based on Data Model and Business Rule. The Application will honor the delete rule (CASCADE, NO ACTION, etc) specified in the Data Model.
- The Purge process is similar to Delete except the delete rule won't be enforced. This is force delete. However, the delete rule specified in database for Foreign key will be enforced by the database.
- The Cleanup process is used to cleanup source tables on exist/not exist criteria on the corresponding target tables. For example, a cleanup job can be set to delete all the Work Orders from a source table if it exists in the target table. It can also be setup to delete based on not exist condition. If a Data Model is specified, the data from the related tables will also be deleted.
