Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
IBM Cognos Business Intelligence

You're reading from   IBM Cognos Business Intelligence Discover the practical approach to BI with IBM Cognos Business Intelligence

Arrow left icon
Product type Paperback
Published in May 2013
Publisher Packt
ISBN-13 9781849683562
Length 318 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Dustin Adkison Dustin Adkison
Author Profile Icon Dustin Adkison
Dustin Adkison
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

IBM Cognos Business Intelligence
Credits
Foreword
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. IBM Cognos Connection 2. Introducing IBM Cognos Workspace FREE CHAPTER 3. IBM Cognos Active Reports 4. IBM Cognos Mobile 5. IBM Cognos Query Studio 6. IBM Cognos Analysis Studio 7. IBM Cognos Workspace Advanced 8. IBM Cognos Report Studio 9. IBM Cognos Framework Manager 10. Administration and Performance Tuning 11. Streamlining Common Administrator Tasks 12. User Adoption Index

Three-tier approach to model design


When designing a model in IBM Cognos Framework Manager, the recommended approach is to use a tiered design. The most common is a three-tier design. In a three-tier design, you will include a database layer, a business layer, and a presentation layer. There is some debate within the Cognos community as to whether or not the third tier is really necessary or if it is better to combine the business layer and presentation layer into one to make it a total of a two-tier model. While this can be done and works great in most scenarios, there are reasons for creating the habit of using a three-tier approach.

One major reason for using the database view layer is that it allows you to import your table structures exactly as they exist in the underlying database. By not changing anything here, you protect yourself against potential issues in case the underlying database tables change. In the database layer, some purists will not even import relationships because of...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime