Data integrity is a fundamental aspect of storage security and reliability. But as the volume of the data increases old data may be moved and stored as archived data to achieve space and time efficiency. Integrity constraints validate data in the operational/active database only. This checking is always carried out at the operational site. The data that is going to be archived and stored separately is never consulted for integrity and consistency. In some organization, new data needs to be checked against both the operational and archived data before it is stored in the database. An example of such data is biometric data where human DNA code can not be duplicated. Captured data whether it is in the operational or archived database, must be consulted to ensure uniqueness of DNA code for new updates. Our work deals with this issue by first storing some meta and actual data during the export operation to the archived database. Later when new updates are made to the operational data, integrity of the incoming data is checked against this derived data which basically represents the whole archive data set. Because it is possible that the same record that is going to be added to the operational dataset may violate integrity of primary key, foreign key, range integrity or unique integrity of archive database. The proposed work utilizes the beneficial aspect of integrity constraints which plays a vital role in maintaining integrity between operational database and its corresponding archive databases.