Archival of Table from ODS
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 10
- Joined: Fri May 14, 2010 4:53 am
Archival of Table from ODS
HI i want to archive the data from ods for 2 years how can i achive this purpose?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 10
- Joined: Fri May 14, 2010 4:53 am
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
You are unqualified to fulfill this requirement and you should pass it on to someone who is. The fact that you cannot describe what you are trying to do is ringing alarm bells. I don't know if you are archiving two years of data, or archiving data for the next two years, or archiving data that is more than two years old.
Describing archiving as running a "script" is another alarm bell. That is woefully inadequate for a data archiving solution. Archiving requires all the normal phases of information development - requirements, analysis, design, build and test. Have a look at how the MIKE2.0 methodology describes this process: http://mike2.openmethodology.org/wiki/I ... n_Offering.
If you are indeed removing data from an Operational Data Store you need a functional requirements document - what data needs to be archived? Does archived data needs to be available in lower tier storage? Is there anything currently using that data? How to you maintain the referential integrity of the database? How do you remove the data and then delete it? How do you automate the process so it can be repeated at regular intervals? How do you perform system integration testing to ensure you haven't broken anything once the archive is executed? etc.
Describing archiving as running a "script" is another alarm bell. That is woefully inadequate for a data archiving solution. Archiving requires all the normal phases of information development - requirements, analysis, design, build and test. Have a look at how the MIKE2.0 methodology describes this process: http://mike2.openmethodology.org/wiki/I ... n_Offering.
If you are indeed removing data from an Operational Data Store you need a functional requirements document - what data needs to be archived? Does archived data needs to be available in lower tier storage? Is there anything currently using that data? How to you maintain the referential integrity of the database? How do you remove the data and then delete it? How do you automate the process so it can be repeated at regular intervals? How do you perform system integration testing to ensure you haven't broken anything once the archive is executed? etc.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: