Best practices and trends in people soft
2 likes1,646 views
The document discusses best practices and trends for archiving Oracle PeopleSoft Enterprise application data. It notes the explosive growth of data in databases and organizations' need for data lifecycle management and archiving. Archiving PeopleSoft data can provide benefits like improved performance, reduced storage costs, faster backups, and compliance with data retention requirements. The document outlines how Solix's archiving solution can archive transactional and historical data from PeopleSoft based on parameters like business unit, date range, and module.
Best practices and trends in people soft
- 1. Best Practices & Trends for Archiving Oracle PeopleSoft Enterprise Applications Data Jnan Dash Executive Consultant Vishal Rao Senior PeopleSoft Consultant
- 2. Agenda Evolution of the Database The Personal Petabyte Explosive Data Growth Solix Enterprise Data Management Suite Need for Archiving PeopleSoft Specific Archiving Benefits Data: The Growing Currency of the Digital Age Archiving PeopleSoft Enterprise Data
- 3. Data: The Growing Currency of the Digital Age
- 4. DBMS Evolution 1960’s File Systems 1970’ s 1st Generation DBMS Data = Shared Resource 1980’ s Relational Technology End-User/Programmer Productivity 1990’ s New data types Scalability Web Support Unstructured Data 2000+ Collaboration Web-scale Mining Big Data, NoSQL
- 5. The Personal PetaByte? It’s coming (2M$ in 2002…2K$ in 2012) Today the pack rats have ~ 10-100GB 1-10 GB in text (eMail, PDF, PPT, OCR…) 10GB – 50GB tiff, mpeg, jpeg,… Some have 1TB (voice + video). Video can drive it to 1PB. Online PB affordable in 2 years. Get ready: tools to capture, manage, organize, search, display will be big requirement. GigaByte TeraByte PetaByte ExaByte
- 6. Databases (== SQL) VLDB survey (Winter Corp). 10 TB to 100TB DBs. Size doubling yearly Riding disk Moore’s law 10,000 disks at 18GB is 100TB cooked. Mostly DSS and data warehouses. Some media managers Unstructured data mostly in files GigaByte TeraByte PetaByte ExaByte
- 7. DB iFS DB2: leave the files where they live Referential integrity between DBMS and FS. Oracle: put the files in the DBMS One security model One storage management model One space manager One recovery manager One replication system One thing to tune. Features: transactions,…. GigaByte TeraByte PetaByte ExaByte
- 8. Mergers & acquisitions Organic business growth Internet Commerce ERP/CRM Records retention: Healthcare – HIPAA Pharmaceutical – 21 CFR 11 Financial – IRS and SEC Rule 17a-4 Data multiplier effect According to industry analysts, annual compound growth rates for databases will exceed 125% Explosive Database Growth
- 9. Challenges from Data Growth What happens? More Data = Less Performance Performance Tuning Money spent on operations vs. Strategic Initiatives SQL Tuning Database Tuning Increased storage costs Longer backup and recovery cycles No data lifecycle management – Compliance & Legal risks Moving Platforms (HP-UX to Linux) More data = Longer Outage Clones
- 10. The Ongoing Problem IT Resources Downtime Risk Compliance $ How many copies?
- 11. Actual Data Burden = Size of production database + all replicated clones The Data Multiplier Effect 200 GB Production 200GB Backup Disaster Recovery 200GB 200GB Test 200GB Development 200GB Quality Control 1200GB Total
- 12. Evolving Business Value Value Time Inactive Data Historical Data Active Data Access Frequency
- 13. Define Storage Strategies Value Time Historical Data Access Tier 1 Tier 2 Tier 3 Active Data Inactive Data Historical Data
- 14. Solix Enterprise Data Management Suite
- 15. Solix EDMS Database Archiving
- 16. Main Points summarized.... Data is the “currency” of the digital age “ Oxygen” for the enterprise (business-critical) Explosive growth in data Causes performance slowdown Increases TCO Need to outline an ILM Policy Data lifecycle management - archival to disposal, Application retirement Pre-requisite to Cloud deployment
- 17. Archiving PeopleSoft Enterprise Data
- 18. Need for Archiving Downgraded response time of PeopleSoft pages More time to retrieve transactional data Increase in execution time for batch processes and reports Execution time of conversion script beyond cutoff window during PeopleSoft Upgrade Significant increase in the size of the backup instance Increasing hardware and storage cost
- 19. PeopleSoft History Data History data needs to be maintained for : Long term data retention requirements Past Payroll data Previous fiscal year books of account Providing better response to existing customers Customer problems/issue logs Regulatory Compliance Check handling in Banking Domain
- 20. PeopleSoft Archiving: Input Parameters PeopleSoft Specific Parameters for Archival : Business Unit Option Archives information from specific business unit or all units Cut off Date Data will be archived based on the cutoff date Module Specific Parameter General Ledger : Journal or Ledger Payroll : Pay Group Purchasing : Requisition or Purchase Order
- 21. PeopleSoft Archiving: Transactional Data Transactional Data includes : Purchasing Module PO Header, line, shipment, distribution details Approval details Change Order and Dispatch information Accounts Payable Voucher & Payment details General & Ledger Journal & Ledger information Time and Labor Payable Time & Reported time details Billing Invoice information
- 22. PeopleSoft Archiving: Archive Constraints Data is archived based on specific constraints: Ledger Ledgers with unposted Journals cannot be archived Asset Asset should be retired Requisition Requisition not linked to purchase order must be closed Vouchers Vouchers with unposted Payment cannot be archived Payroll Payroll needs to be finalized before archival
- 23. Transaction Link Archiving Process needs to take of Transactional Links Example : Purchase Order – Requisition in Purchasing Module (C) -- Closed (O) -- Open Purchase Order 3 (C) Purchase Order 2 (C) Purchase Order 1 (C) Requisition 1 (C) Requisition 2 (C) Requisition 3 (O) Requisition 4 (O)
- 24. Benefits Faster execution of data in Production system Merge View access to see current and archived data No impact on processes, reports or panels Faster upgrades & migrations Upgrade of archived data possible to higher application version Reclaim Storage Space & Backup tapes
- 25. Case Study – A leading Travel & Transportation Organization in Europe Client is a leading travel and transportation organization in Europe Client Description Application : CRM 8.4 PeopleTools 8.44 Modules : Call Center Marketing Customer Database : Oracle Operating System : Sun Solaris Technology Excessive database growth Poor user response time Application upgrade which will cause long outage to business Excessive backup and recovery times Current Status Database is large, growing steadily Current DB size is around 3 TB Custom tables take around 75% of space. Top 15 largest tables takes over 50% of space Data Condition Data Archiving for specific module which will result in the following: Upgrade Conversion Scripts will be completed within the cutoff window Saving on Storage Costs; using Cheaper Disks to store Archived Data Reduction in the Backup Window with smaller footprint of Production Instance Effort towards fine tuning activity also reduce s proportionately freeing up skilled resources for other tasks Increased application response time as application now looks at smaller data volume Recommendation
- 26. Thank You
Editor's Notes
- #13: This graph demonstrates the evolving business value of the data as it moves through the information lifecycle. Typically, enterprise data is used most frequently, and is therefore most valuable around the time it is created or acquired. An example might be this month’s financial transaction data. Next year, however, this information will be used mainly for reporting purposes, and will have a lower value. In five years, its utility and value will decline even further. <Click> Remember though, as we stated in the last slide: even decades-old historical data can rise in value if it is required to satisfy a compliance or discovery request. This slide demonstrates an increase in the business value of a particular set of data.
- #14: How does the storage infrastructure map to the evolving business value of enterprise data? <Click> Typically, corporations choose to store the data pertaining to current business transactions on high-performance online storage media for optimum retrieval and processing speed. <Click> Reporting data from prior periods is still used frequently, but can be stored on a somewhat slower near-line storage medium. <Click> Finally, historical data has the lowest value, and can be stored offline; for example on low-cost tape or optical storage. The trade off is that, when historical data is requested, it will take extra time for a staff member to locate and mount the correct tape and then retrieve the data.