Scribd
Upload
48 views6 pages

Elixtra Data Purging/Archive: Purpose of Document

This document discusses purging and archiving data from the Elixtra project database to reduce its size over time. It outlines two approaches for purging unwanted data: 1) after taking a full database backup, or 2) without a backup. The commenter recommends documenting dependent entities, foreign keys, and deletion specifications for independent entities. Procedures should be added to mark records as removed rather than deleting them permanently. Relations between tables storing member data are also documented to understand dependencies before purging old timesheet, payroll, alert, activity, employee and requisition information.

Uploaded by

phone2hire
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
48 views6 pages

Elixtra Data Purging/Archive: Purpose of Document

This document discusses purging and archiving data from the Elixtra project database to reduce its size over time. It outlines two approaches for purging unwanted data: 1) after taking a full database backup, or 2) without a backup. The commenter recommends documenting dependent entities, foreign keys, and deletion specifications for independent entities. Procedures should be added to mark records as removed rather than deleting them permanently. Relations between tables storing member data are also documented to understand dependencies before purging old timesheet, payroll, alert, activity, employee and requisition information.

Uploaded by

phone2hire
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Elixtra Data Purging/Archive

Purpose of Document
The Elixtra project is an end to end organizational project that has functionality to store all
Organizations/Vendors/Employees/Applicants/Consultants information those are Exists or those are deleted by user. No one data
physically remove from database table if any Elixtra user deleted any records by UI only a column IsRemoved value of every table will be
switched to 1 from 0. So in next time those data are not able to view in website.
Thats the reason database of Elixtra project will become huge. And if any Client wants to remove all these data that are not need
now or in coming days then our application doesnt have any system to delete these data permanently.
In this context there are two way to purge unwanted information
1. Purge the data after full database backup.
2. Purge the data without database backup.

Fazlurs Comment: Data purging and archive should be implemented on the independent entities only. So its necessary to find out and
document the following
List Of Independent Entities i.e Candidate, Employee, Consultant etc
Under each independent entity, list down the dependent entity with foreign key relation detail. The foreign key detail should
include
o Foreign Key Name
o Insert & Update Specification i.e OnDelete & OnUpdate actions
Group the independent entities by OnDelete action
List down the UI pages where the deletion takes place on independent entity by the end user.
Implement OnRemove functionality on the independent entities only. The following should be documented for each independent entity
Add one stored procedure named Entity_RemovedById.
Add dataaccess and faade function for this stored procedure
Call this function on delete action of end user.
Add a where clause IsRemoved=0 to each and every stored procedure which fetch multiple records except any GetPaged
sp. List down the sp names where this has been added.
Pass IsRemoved clause to all GetPaged sp from data access functions. List down the dataaccess function names where this
has been passed.
Please complete this document to incorporate my comments and send to me.

Purge UI Page

1 Elixtra Data Purging/Archive | Created By : Satyendra


Note: We support only full database archival not partially.

Following are list of Member data that we can purge after some time
1. Member Timesheet Info
2. Member Payroll
3. Member Alerts
General Alerts
Member Job Cart Alerts
4. Member Activity
5. Former Employees all relational data
6. Requisition Information
7. Custom Report Saved Queries
Following relational diagram shows the Member Timesheet tables relations

2 | Created By : Satyendra
Following relational diagram shows the Member Payroll tables relations

Following relational diagram shows the General Member Alert tables relations

3 Following are list of Member data that we can purge after some time | Created By : Satyendra
Following relational diagram shows the Member Activities tables relations

Following relational diagram shows the Member Activity tables relations

4 Following are list of Member data that we can purge after some time | Created By : Satyendra
Following relational diagram shows the Member tables relations

Following relational diagram shows the Member Job Cart and Job Cart alerts table relations

5 Following are list of Member data that we can purge after some time | Created By : Satyendra
Following relational diagram shows the Posted Requisition tables relations

Benefits:
Reducing the size of Elixtra database.

6 Benefits: | Created By : Satyendra

You might also like