By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData Collective
  • Analytics
    AnalyticsShow More
    predictive analytics in dropshipping
    Predictive Analytics Helps New Dropshipping Businesses Thrive
    12 Min Read
    data-driven approach in healthcare
    The Importance of Data-Driven Approaches to Improving Healthcare in Rural Areas
    6 Min Read
    analytics for tax compliance
    Analytics Changes the Calculus of Business Tax Compliance
    8 Min Read
    big data analytics in gaming
    The Role of Big Data Analytics in Gaming
    10 Min Read
    analyst,women,looking,at,kpi,data,on,computer,screen
    Promising Benefits of Predictive Analytics in Asset Management
    11 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-23 SmartData Collective. All Rights Reserved.
Reading: Why Use Reporting Repositories for Business Intelligence?
Share
Notification Show More
Latest News
ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence
ai in omnichannel marketing
AI is Driving Huge Changes in Omnichannel Marketing
Artificial Intelligence
ai for small business tax planning
Maximize Tax Deductions as a Business Owner with AI
Artificial Intelligence
ai in marketing with 3D rendering
Marketers Use AI to Take Advantage of 3D Rendering
Artificial Intelligence
How Big Data Is Transforming the Maritime Industry
How Big Data Is Transforming the Maritime Industry
Big Data
Aa
SmartData Collective
Aa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Warehousing > Why Use Reporting Repositories for Business Intelligence?
Business IntelligenceData Warehousing

Why Use Reporting Repositories for Business Intelligence?

DougLautzenheiser
Last updated: 2009/02/09 at 2:09 AM
DougLautzenheiser
6 Min Read
SHARE

I regularly review web statistics with interest to see how Google searches route people to my blog. One person from Indiana came looking for reasons why you should use a data mart. The searcher was probably disappointed since the answer was not really there as advertised. I feel bad, so let me fix that and add some content — perhaps he or she will return.

Rather than use industry business intelligence terms pregnant with political meaning like Data Warehousing and Data Marts, I am using “Reporting Repository,” which I hope is free from bias.

While there are proponents for doing reporting directly against the operational systems’ data (see another blog for some information), it is generally speaking just not a good idea. The main argument is that operational data has live, real-time information. But there is a long list of disadvantages.

Instead of using operational data for reporting purposes, you should provide your end users with a centralized, shared copy created especially for BI: a Reporting Repository.

More Read

embedded bi tools

Embedded BI Tools Bring Huge Benefits to Business Applications

How IoT Can Be Connected to Business Intelligence
14 Brands Using Mobile Apps Instead of Ads to Build Customer Loyalty
5 Vital Business Intelligence Tips All Companies Should Embrace
Impressive Ways that AI Improves Business Analytics Insights

With this term, I mean that the operational and external data feeds have been restructured and stored in a way to make end-user reporting as simple and easy as possible. In addit…


I regularly review web statistics with interest to see how Google searches route people to my blog. One person from Indiana came looking for reasons why you should use a data mart. The searcher was probably disappointed since the answer was not really there as advertised. I feel bad, so let me fix that and add some content — perhaps he or she will return.

Rather than use industry business intelligence terms pregnant with political meaning like Data Warehousing and Data Marts, I am using “Reporting Repository,” which I hope is free from bias.

While there are proponents for doing reporting directly against the operational systems’ data (see another blog for some information), it is generally speaking just not a good idea. The main argument is that operational data has live, real-time information. But there is a long list of disadvantages.

Instead of using operational data for reporting purposes, you should provide your end users with a centralized, shared copy created especially for BI: a Reporting Repository.

With this term, I mean that the operational and external data feeds have been restructured and stored in a way to make end-user reporting as simple and easy as possible. In addition to changing the data structure, the organization has added an abstract layer (master data management, hierarchies, and so forth) as well as a metadata layer.

A team of technical specialists must bear the burden of understanding the complex data one time while creating the reporting repository and the necessary integration processes. Otherwise, the end users are yoked everyday with the burden of trying to write reports against the complex operational data (which is not meant for reporting).

Here are some reasons you should not use operational data for your end-user reporting:

  • Because of critical nature, operational system must be isolated and protected
  • Data is structured for ease of data maintenance, not reporting
  • Since not designed for end-user reporting, there is rarely documentation for doing that
  • Typically, operational system does not physically store all data (uses business rules inside application code)
  • Typically, operational system does not store historical data (only a snapshot of current situation)
  • Typically, operational system does not have an abstract layer for end-user reporting
  • Typically, operational system does not have a metadata layer for end-user reporting
  • Typically, operational data not accessible by common BI tools

Reporting Repositories provide a corresponding solution to each of those operational data problems:

  • Intentionally designed for access with considerations for security, performance, etc.
  • Data is structured for ease of reporting
  • Intentionally designed and documented for end-user user
  • Either physically stores calculated columns or exposes virtual columns
  • Captures historical information for auditing, comparisons, trending
  • Provides abstract layer to provide context for understanding information
  • Provides metadata layer to provide explanations for accessing and using information
  • Designed to be accessed by BI tools

But what are you going to put in your Reporting Repository? Well, you will figure out the design and content based on the needs of your business decision makers. If you want to build an enterprise repository to serve any and all reporting purposes, you are looking at a Data Warehouse (Bill Inmon approach). If you go with a very specific repository for a unique purpose, you are considering the Data Mart (Ralph Kimball).

Here are the steps for designing your Reporting Repository:

  • Your decision maker needs to take important business action
  • Which requires specific information.
  • Decision maker also needs specific method of interacting with the information (information delivery or interactive, on-demand access)
  • Which determines the proper storage of information in the repository
  • Which determines the requirements for integration with operational systems
  • Which determines the requirements for capturing and storing data within the operational systems

If you came here through Google looking for answers to your BI questions, I hope this helped. If you have any questions, please contact me.

 

BI-Software.Blogspot.com

TAGGED: bi, business intelligence, data warehousing, reporting
DougLautzenheiser February 9, 2009
Share this Article
Facebook Twitter Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence
ai in omnichannel marketing
AI is Driving Huge Changes in Omnichannel Marketing
Artificial Intelligence
ai for small business tax planning
Maximize Tax Deductions as a Business Owner with AI
Artificial Intelligence
ai in marketing with 3D rendering
Marketers Use AI to Take Advantage of 3D Rendering
Artificial Intelligence

Stay Connected

1.2k Followers Like
33.7k Followers Follow
222 Followers Pin

You Might also Like

embedded bi tools
Business Intelligence

Embedded BI Tools Bring Huge Benefits to Business Applications

5 Min Read
internet of things and business intelligence
Internet of Things

How IoT Can Be Connected to Business Intelligence

6 Min Read
businesses using mobiles app for success
Big Data

14 Brands Using Mobile Apps Instead of Ads to Build Customer Loyalty

19 Min Read
tips for making the most of business intelligence
Business Intelligence

5 Vital Business Intelligence Tips All Companies Should Embrace

7 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai in ecommerce
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence
AI and chatbots
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive

Quick Link

  • About
  • Contact
  • Privacy
Follow US

© 2008-23 SmartData Collective. All Rights Reserved.

Removed from reading list

Undo
Go to mobile version
Welcome Back!

Sign in to your account

Lost your password?