on 2010 Dec 23 10:00 PM
Hi,
Currently in our project, the change log retention is done for one year. But it is occupying huge amount of space. Please let us know the best practices for retention of change log table data in production system. What would be the ideal period for which change log data needs to be retained.
Thanks in advance!
Regards,
Rathy
Request clarification before answering.
Hello,
I completely agree with all forum mates comment on defining retention period based on business.
I can add up saying that even after archiving User can see the change logs from same business document so from Users point of view there will be no changes but from technical point of view this archived change logs are coming from archive server.
You could be aggressive with this change log for 6 to 8 months retention period
- As percentage User displaying change log will be lesser
- As it is convenient to users to still see the archived change log
- To reduce the burden on database
With this you may achieve more than 20% more archiving of change logs.
.
Hope this will benifit you.
-Thanks,
Ajay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I don't think there's a hard and fast rule. It's what you are comfortable with.
Ask yourself when was the last time you had to use it (?)
We have a 14TB system and the space is scarce, so we delete the change log each month.
Haven't had any problem whatsoever. But opinions vary.
-RMP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A better way is to set up a cut-off date for the cube or data targets where the change log is sued to run the delta update.
If it has been verified, the period has been closed in the source systems, then you can delete it. You already have it set for one year but if it is causing a huge load on the system- maybe it is time for the business to revaluate that process?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rathy,
Here it is project decision to retain change log for one year but if it cost you in term of storage space then batter to keep it less period like six months. even if some data discrepancy happen then PSA request will be there to solve.
To find a best practice you need to know how frequently data going to change for perticular DSO, then you can take decision for change log retaining period.
Regards,
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
30 | |
10 | |
8 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.