Designing a 300TB Data Warehouse with ASM

Designing a 300TB Clustered Data Warehouse

• Introduction
• Project Overview
  • Architecture Review (The Two Platforms)
  • The Chosen One – The one to model
  • The Platform Phases
• The Power of Partition Exchange
  • Loading Data
  • Updates without UPDATE
• ASM: Performance and Management Made Easy
  • Storage Infrastructure
  • Availability
  • Performance
  • Backup & Recovery
• Trade Offs
• Lessons Learned/Tips & Tricks

Project Overview

• The Challenge:
  • Two different CDR platforms architectures.
  • Two different tools, technology and resource skills.
  • Two different data retention and access methods serving the same customers.
• The Solution:
  • One common platform architecture for both systems to meet the user community requirements.

The ‘Consolidation’ Project

Develop the Sprint CDR application leveraging the Nextel architecture.

• Build it on a Sun/Oracle/DataStage/Business Objects platform.
• Align the data content lifespan between the two platforms.
  • Allow for 24 months of call data in the new platform to meet the requirements of the Legal/Subpoena department.
• Continue to meet the SLA of making records accessible within 30 minutes of receipt.

© 2010, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

1. How to view and edit data on ASM using BBED
2. Using udev with Oracle Architecture (RAC & ASM)
3. 利用Toad for Data Analysts软件生成查询语句
4. Extending Automatic Storage Management to Manage ALL DataOracle Database 11g Release 2
5. Oracle Secure Backup:Secure Your Data, Protect Your Budget
6. Data gathering for troubleshooting Oracle Real Application Cluster issues
7. Exadata and Database Machine 11.2
8. Oracle DUL(Data Unloader) User Guide and Downloads
9. Data Gathering for Troubleshooting RAC Issues
10. SQL*Net PERFORMANCE TUNING UTILIZING UNDERLYING NETWORK PROTOCOL