Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

Performance

Performance

For retirement projects, the Data Vault Loader process runs for days.
When you build retirement entities, do not use one entity for all of the source tables. If an entity includes a large number of tables, the Data Vault Loader may have memory issues. Create one entity for every 200-300 tables in the source application.
You can use a wizard to automatically generate entities. Or, you can manually create entities if you want the entities to have special groupings, such as by function or size.
When you create entities with smaller amounts of tables, you receive the following benefits:
  • The Data Vault Loader job performance increases.
  • Reduces staging space requirement as the retirement project uses less staging space.
  • You can resolve code page configuration issues earlier.
  • You can start to validate data earlier with the Data Validation Option.
  • Overall, provides better utilization of resources.

0 COMMENTS

We’d like to hear from you!