During normal use over a long period of time or use in very large installations, your primary FactoryLogix Database may reach a point where it becomes unacceptably large. Certain tables, such as those holding machine data or batch processing information, can grow to hold large numbers of records, while other tables storing items such as visual aids and documents can hold large amounts of data in individual records.
To assist your data management needs, FactoryLogix 8.181.0.0 and higher includes a powerful data archiving solution. When enabled, you can archive old or unwanted batches, assemblies and related processes, receiving processes, and machine performance data to a separate database.
FactoryLogix data archiving has the following components.
Component | Description |
|---|---|
Archive service | A Windows service that runs continuously on the FactoryLogix Application Server and processes archival data. See Initial setup for archiving. |
Archive Database | A separate SQL database that you create on the same SQL server instance as the operational FactoryLogix Database. See Initial setup for archiving. |
Data archiving license key | Purchased from Aegis and required to enable archiving. |
Archiving window | A window you access from NPI System Configuration with options to configure and control data archiving, restoring, and associated scheduling. |
Production client application | Additional support for the Trace window that allows you to review archived records. |
General process flow
When a record is no longer needed in the operational FactoryLogix Database, you can schedule it for archiving using the Archiving feature in the NPI client application. You can also configure the system to select records for automatic archiving based on criteria such as the age of the records.
If you need a previously-archived record in the operational FactoryLogix Database again, you can restore the record manually. Records scheduled for archiving or restoring are listed in an archiving queue. Every fifteen minutes, the Archive service checks the queue and moves selected records either to or from the archive database.
Important
We recommend scheduling records for archiving and restoring during off-peak hours to avoid potential issues related to processing records while users are accessing records in the operational database. In addition, the amount of time to process records may vary depending on system performance and the type of record. For example, a batch that has multiple serial numbers associated with it may take longer to archive than a process revision.
Related topics |
|---|