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 OWB code artifacts


Code artifacts are normally time consuming and difficult to obtain. Oracle Warehouse Builder is no exception to this rule.

Getting ready

Subversion is an ideal place to store this kind of information. It is important to have a standard naming convention for where and how the code resides within Subversion. All incremental releases within the development environment and test environments are no longer important, when you hand over the code. It is important to have a single baseline of the code, in order to effectively hand over the environment.

How to do it...

Subversion is ideal to track code and changes to code. In order to do this effectively, code should be checked in at a level of granularity that will allow you to manage individual objects as follows:

  1. 1. Create a folder that relates to the target environment, say Production, as shown in the following screenshot:

  2. 2. Create a subfolder named OWB for the technology component under Baseline within the Production...