The curriculum of BIT660 outlines a structured approach to archiving, typically divided into the analysis of data, the configuration of archiving objects, and the execution of the archiving process.
Using database monitors like (Database Performance Monitor) or DB12 , administrators identify tables based on two major metrics:
Data Archiving addresses these challenges by moving inactive data from the live production database to secure, compressed archive files. This is fundamentally different from a , which is a short-term copy for disaster recovery. Archived data is removed from the live system but remains accessible for reporting and audits, whereas backups are not designed for regular data access. bit660 data archiving pdf 23
Comprehensive Guide to BIT660 Data Archiving: PDF 23 Highlights
Before diving into the "how," it's important to understand the "why." SAP systems naturally accumulate massive amounts of transactional data—from financial documents (FI) and sales orders (SD) to purchase orders (MM) and production orders (PP). Without proper management, this data accumulation leads to severe issues: The curriculum of BIT660 outlines a structured approach
The beauty of this document is that it focuses on the universal "general way of archiving," ensuring the skills you learn for one object are transferable to others.
Only after the system verifies that the archive file was written correctly does it go back and delete the original records from the database tables. 5. Keeping It Reachable (Access and Retrieval) Archived data is removed from the live system
The central element (defined in T-code AOBJ) that determines which data is archived (tables) and which programs are used.
Covers structure of archiving objects, file names/paths, and specific settings for write/delete programs.
The ability to move data to cost-effective storage solutions reduces the cost of high-performance DB storage. 5. Conclusion