|Building a Data Warehouse|
|Written by Stephen Forte|
|Tuesday, 14 September 2010 02:16|
Most developers are scared of “Business Intelligence” or BI. Most think that BI consists of cubes, pivot/drill down apps, and analytical decision support systems. While those are very typical outcomes of a BI effort, many people forget about the first step, the data warehouse.
Typically this is what happens with a BI effort. A system is built, usually a system that deals with transactions. We call this an OLTP or on-line transaction processing system. Some time passes and reports are bolted on and some business analysts build some pivot tables from “raw dumps” of data. As the system grows, reports start to slow since the system is optimized to deal with one record at a time. Someone, usually a CTO type says: “we need a BI system.” A development effort is then spent to build a data warehouse and cubes, and some kind of analytical system on top of those cubes.
- Step by step guide on installing PowerPivot for SharePoint on a single machine
- List of PowerPivot DAX functions with description
- How to install PowerPivot for Excel and list of know issues
- List of suggested datasets to test PowerPivot
- Q: How can I calculate difference between two dates in DAX (seconds, minutes, hours, days and months)
- Learning PowerPivot and DAX
- Using Power Pivot and Power View for Profit Analysis
- Microsoft Virtual Lab: PowerPivot for Excel 2010 Introduction