370 likes | 572 Views
Information Lifecycle Management for Oracle Apps Data. Erik Jarlstrom Director of North American Pre-sales. What does this have to do with Oracle Databases?. Corporate Summary. Founded in 1989 Over 2000 customers in 30 Countries
E N D
Information Lifecycle Management for Oracle Apps Data Erik Jarlstrom Director of North American Pre-sales
Corporate Summary • Founded in 1989 • Over 2000 customers in 30 Countries • Committed to providing enterprise database archiving and test data management solutions • Reputation of high quality and reliable products • Partners with industry leading database and storage solution providers • Recognized by Gartner, Giga, and Meta as database archiving market leader
Agenda • Database Growth and Impact • Strategy: Information Lifecycle Management • Active Archiving • Enterprise Database Archiving
Database Growth Impacts IT Budgets “…databases will grow 30x during the next decade, or roughly 40% annually.” Source: Meta Group 2001 40% CAGR may be a conservative estimate! “With growth rates exceeding 125%, organizations face two basic options: continue to grow the infrastructure or develop processes to separate dormant data from active data.” Source: Meta Group 2003
Related Symptoms • Application users complain their system is “slow” to: • Perform online account inquiries and financial period closeouts • Enter transactions and process payments • Post batches and generate reports • Process weekly/monthly/quarterly depreciation runs • Increasing operating costs • Higher hardware and software license and support costs • Longer development and test cycles • Labor intensive time and effort for system administrative tasks • Extended maintenance times for managing backup, recovery and cloning processes • Additional headcount required to adequately manage a larger environment
Potential Solution: Ignore Database Growth …and continue to add • People • Processes • Technology …and continue to decrease • Performance • Availability • Time for other projects ProductionDatabase
Traditional Approaches • Add More Capacity • Bottom line impact • Uncontrolled continuous cost • Institute rigorous database tuning • Does not directly address data growth • Reaches point of diminishing returns • Delete Data (i.e. Purge) • Legal and retention issues • Data may be needed for data warehousing • In-House Development • Complex undertaking • Application specific • Support / upgrade / maintenance / opportunity cost
Acquisition of Data Heavy Access Disposal Rare Access Medium Access Strategy: Information Lifecycle Management • Understand data retention requirements • All data has a life cycle from acquisition to disposal • Define availability level requirements • At various stages, data has different: • Business value • Access requirements • Performance requirements • Implement storage strategy to meet availability requirements • Each stage should be stored on the appropriate type of storage • Segregate application data to support strategy • Data should be managed to match the business value
© 2003 Enterprise Storage Group, Inc. Source: Enterprise Storage Group, May 2003 Matching Access and Performance to Business Value
Implement Storage Strategies to Meet Availability Requirements RDBMS and High-Concurrency Storage (RAID) RDBMS, File Systems, NAS, Optical Tape or Optical Storage
Segregating Application Data to Support Storage Strategy ORDER_DATE > 01-JAN-2002 ORDER_DATE > 01-JAN-1998 & < 31-DEC-2001 ORDER_DATE < 31-DEC-1997
Information Lifecycle ManagementArchiving Strategy “Off-LineArchive” “On-LineArchive” “Current” “History/Reporting” Path 1 Archive Archive ProductionDatabase Archive Database Tape Flat Files Archive Restore Restore Years 1 - 2 Years 3 - 5 Years 6 - 7 Years 8+ (Adjust timeframes to meet internal & statutory requirements)
Archive Database Archive Files Production Database Archive Files Data Access (locate, browse, query, report) Solution: Active Archiving • Reduce amount of data in the application database • Remove obsolete or infrequently used data • Maintain “business context” of archived data • Archive relational subsets vs. entire files • Enable easy user access to archived information • View, research and restore as needed • Support Data & Storage Management Strategies Archive & Restore
Archiving Oracle Apps Data Archiving Historical Data Archive Database GL – Balances, Journals … AP – Payments, Invoices, Vendors… AR – Receipts, Invoices … FA – Depreciation, Adjustments Purchasing – POs, Reqs, OM – Orders, … INV - Transactions General Ledger Payables Production Database Receivables Assets Locate, Browse, Query, Report . . . Data Access
Production Transparent Access - Forms
Archive Transparent Access - Forms
Archive & Production Transparent Access - Forms
Production Transparent Access - Reports
Archive Transparent Access - Reports
Archive & Production Transparent Access - Reports
Top Requirements for Enterprise Database Archiving • Extract subsets of related data to offload • Able to go beyond catalog-defined relationships • Selectively/relationally delete all or some archived data • Selectively/relationally restore • Access, browse, query archived data • Preserve business context of archived data • Comprehensive archive data management • Architecture for long term enterprise-wide strategy
Manage Your Enterprise Data Smarter Test Smarter with Relational Tools Store Smarter with Active Archive Solutions Pre-Production (Test, Dev, Training, …) Production PeopleSoft ClarifyCRM Oracle Apps RelationalTools Archive for Servers Archive for DB2 Relationship Engine Legacy Oracle SQL Server DB2 UDB DB2 Sybase Informix
Suggested Resources • Databases on a Diet: Meta - Jan 2003 • Banking on Data: InformationWeek – Aug 4, 2003 • Bank of New York implements active archiving • Enterprise Storage Group (ESG) Impact Report on Compliance - May 2003 • The effect on information management and the storage industry • Princeton Softech’s Web site and whitepapers www.princetonsoftech.com
Questions Erik Jarlstrom Princeton Softech ejarlstrom@princetonsoftech.com 916.939.8191