Escolar Documentos
Profissional Documentos
Cultura Documentos
Bob Cohen
Sense Corp
October 2001
Presentation Overview
Introduction Overview of aggregate awareness Aggregate awareness in Business Objects RDBMS materialized views for aggregate awareness Examples of each architecture Architectural trade offs Q&A
Introduction
It is the ability to dynamically re-write SQL to the level of granularity needed to answer a business question Allows for faster querying speed
Document_Id Line_Item Customer_Id Dollars
Customer_Id Dollars
1,000,000 Rows
5
1,000 Rows
Define contexts
All aggregated facts physically created during extraction, transformation, and load (ETL)
Increase the query speed of very large data sets Physically stores aggregated and joined data sets at the database level Can create both simple and complex views Different from traditional database views
Simple views
Selects rows from only one table Cannot perform any joins, group by functions, or connect by functions Complete refresh of data required
Complex views
SQL
Query Result
Query re-write needs to be enabled at the database or session level Following permissions need to be set up for each user that can create a materialized view
Create materialized view Create table Create view Create index Unlimited or sufficient space
To use the alter query execution path functionality, you must set up a dimension
Each materialized view needs to be coded with a create statement on the database Analyze statistics in order for optimizer to recognize materialized views Can create an index on materialized view
Architectural Trade-Offs
Business Objects Code Location Metadata Objects created at the universe level Allows for centralized metadata repository Tables physically created through ETL process RDBMS
1-3
ETL
Architectural Trade-Offs
Business Objects Source Specific Can be used against any source RDBMS
2-3
RDBMS must support materialized views; if multiple sources, need to be maintained in each database
Re-Write Location
Re-written in RDBMS
Architectural Trade-Offs
Business Objects RDBMS
3-3
Visible SQL
Yes
No
Design Option 1
Do Not Implement any Aggregate Awareness
Keeps design simple Speed is not always a requirement Not all reporting requires aggregation Users know data well enough to know which tables to query
Design Option 2
Implement Aggregate Awareness through BusinessObjects Exclusively
Not every database source supports materialized views Materialized views need to be maintained in every database source
Design Option 2
SQL Server
BO Repository
Oracle 8i
MS Access
Design Option 2
Implement Aggregate Awareness through BusinessObjects Exclusively
Need for centralized metadata repository Do not have access to a strong DBA Closed reporting architecture
Design Option 3
Implement Materialized Views in RDBMS
Design Option 3
BO
Data Warehouse
MS Access
Design Option 3
Implement Materialized Views in RDBMS
Need quick results Access to strong DBA Simplify universe design Have one or few sources Do not need a centralized metadata repository
Design Option 4
Implement Both Materialized Views in RBDMS and Aggregate Awareness in BusinessObjects
Willing to deal with complexity Recognizes advantages in both approaches Able to define advantages for each architecture
Design Option 4
Q&A