Book Image

Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology

By : John Heaton
Book Image

Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology

By: John Heaton

Overview of this book

Oracle Database 11g is a comprehensive database platform for data warehousing and business intelligence that combines industry-leading scalability and performance, deeply-integrated analytics, and embedded integration and data-quality all in a single platform running on a reliable, low-cost grid infrastructure. This book steps through the lifecycle of building a data warehouse with key tips and techniques along the way. Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology outlines the key ways to effectively use Oracle technology to deliver your business intelligence solution. This is a practical guide starting with key recipes for project management then moving onto project delivery. Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology is a practical guide for performing key steps and functions on your project. This book starts with setting the foundation for a highly repeatable efficient project management approach by assessing your current methodology to see how suitable it is for a business intelligence program. We also learn to set up the project delivery phases to consistently estimate the effort for a project. Along the way we learn to create blueprints for the business intelligence solution that help to connect and map out the destination of the solution. We then move on to analyze requirements, sources, and data. Finally we learn to secure the data as it is an important asset within the organization and needs to be secured efficiently and effectively.
Table of Contents (21 chapters)
Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface

Creating your application schema


The APEX application will connect to a database schema. It is recommended that all database objects be placed into their own separate schema. By separating these objects, you ensure that the data cannot be compromised in other areas within the data warehouse.

Getting ready

With a separate schema for the APEX application, it segregates the objects from the source table information stored within the staging schemas. This segregation makes for easier maintenance and security of the tables.

How to do it...

When building an APEX application, you first need to select the schema to which you want to connect. If there are additional tables in this schema, it would be possible for a screen to be built directly on the data warehouse tables.

  1. 1. Firstly, we will create a database user, app, to be the schema owner:

    create user app identified by app
    default tablespace users
    temporary tablespace temp;
    
  2. 2. Assign roles and privileges to the schema owner:

    -- Default roles for demo...