Book Image

Oracle Business Intelligence 11g R1 Cookbook

By : Cuneyt Yilmaz
Book Image

Oracle Business Intelligence 11g R1 Cookbook

By: Cuneyt Yilmaz

Overview of this book

<p>Extracting meaningful and valuable business information from transactional databases is crucial for any organization. OBIEE 11g is a reporting tool that satisfies all the business requirements regarding complex reporting. It consists of a powerful back-end engine with a repository and a highly customizable graphical web interface.</p> <p>Oracle Business Intelligence 11g R1 Cookbook provides all the key concepts of the product including the architecture of the BI Server. This practical guide shows each and every step of creating analytical reports starting from building a well-designed repository. You will learn how to create analytical reports that will support different business perspectives. <br /><br />This practical guide covers how to implement OBIEE 11g suite in order to enable BI developers to create sophisticated web based reports. All of tasks will be covered step by step in detail. <br /><br />You will explore the architecture of the Oracle Business Intelligence Server and learn how to build the repository (RPD). We will also discuss how to implement the business rules in the repository with real-life scenarios.</p> <p>Best practices of a successful BI implementation are esssential for any BI developer so they are also covered in depth.If you are planning to implement OBIEE 11g suite, this step-by-step guide is a must have resource.All the key tasks are defined in detail and supported with diagrams and screenshots.</p>
Table of Contents (19 chapters)
Oracle Business Intelligence 11g R1 Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Best practices of the analyses and the dashboards


The queries that are executed against the data warehouses cause a large amount of database processing. Every time we access an analysis, the query is going to be generated by the BI server and it's executed against the database. Let's assume that a dashboard contains many analyses that will cause intensive calculations. When the business users access that dashboard, all the analyses will run. This will impact the performance. We should not publish many objects in the main dashboards. The users should see the results as quickly as possible. We can achieve this by publishing summary result sets in the main dashboards. If they are interested in the finer granular levels, they can drill down or navigate to another analysis that contains the details.

How to do it...

  1. Create the dashboards based on the roles or the functionality area.

  2. Use the Dashboard Pages to divide the content, to enable end users to focus on the data.

  3. Avoid designing dashboards...