Business Intelligence Portfolio


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Business Intelligence Portfolio

  1. 1. BUSINESSINTELLIGENCE PORTFOLIO<br />Chris Seebacher<br />September 11, 2009<br /><br />
  2. 2. Table of Contents<br />This portfolio contains examples that were developed while participating in the SetFocus Microsoft Business Intelligence Masters Program.<br />
  3. 3. DATA MODELING<br />
  4. 4. Relational Physical Model of the database used in a team project. This database tracked evaluations submitted by students and was used to build a series of charts and reports that allowed instructors to see how they were performing over a variety of metrics. <br />
  5. 5. Data Model of a Star Schema used to create a staging area to import data for a project. This project was used to track book sales by author, customer and region. Examples how it was used are found in the following section.<br />
  6. 6. SQL PROGRAMMING<br />
  7. 7. The queries in this section used the staging area shown in the previous section. This query returns all publishers with books that are currently out of stock, quantities still needed, and order status, ordered by greatest quantity needed first .<br />SELECT <br />books.ISBN, title as [Book Title], PUBLISHER, QUANTITYORDERED-QUANTITYDISPATCHED AS [Quantity Needed], orders.orderid, <br /> case <br /> when orderdate+3 &lt; getdate() and quantityordered&gt;quantitydispatched<br /> then &apos;Needs Review&apos; <br /> else &apos;Standard Delay&apos; <br /> end AS [STATUS]<br />FROM BOOKS <br />inner join ORDERITEMS <br /> on books.isbn=orderitems.isbn<br />inner join orders <br />on orderitems.orderid=orders.orderid<br />WHERE QUANTITYORDERED&gt;QUANTITYDISPATCHED and stock=0<br />group by books.ISBN, title, PUBLISHER, orderdate, orders.orderid, quantityordered, quantitydispatched<br />order by [quantity needed] desc<br />
  8. 8. This query determines the list of countries from which orders have been placed, the number of orders and order items that have been had from each country, the percentages of the total orders, and the percentages of total order items received from each country<br />--Create temporary table <br />select <br /> [Country], <br /> count(OrderNum) as [Total Orders], <br /> sum(QuantityOrdered) as [Total Items Ordered] into #C_Totals<br />from<br />(select right(address, charindex(&apos; &apos;,reverse(address))-1) as &apos;Country&apos;, customers.customerID , <br />orders.orderID as &apos;OrderNum&apos;, orderItems.orderItemID<br />, case<br /> when QuantityOrdered is null<br /> then 0<br /> else QuantityOrdered<br /> end as QuantityOrdered<br />from orders<br />inner join orderItems<br /> on orders.orderID=orderItems.orderID<br />right join customers <br /> on orders.customerID=customers.customerID<br />group by QuantityOrdered, <br />customers.customerID, <br /> address, <br />orders.orderID, <br />orderItems.OrderItemID<br />) as C_Orders<br />group by [Country] with rollup<br />--Query temporary table to extract, calculate and format data appropriately<br />select [Country], [Total Orders], [Total Items Ordered], <br />(convert(numeric(10,4),([Total Orders]/(select convert(numeric,[Total Orders]) <br />from #C_Totals<br />where [Country] is null)))*100) as [% of Total Orders] <br />, (convert(numeric(10,4),([Total Items Ordered]/(select convert(numeric,[Total Items Ordered]) <br />from #C_Totals where [Country] is null)))*100) as [% of Total Items Ordered] <br />from #C_Totals<br />where [Country] is not null <br />group by [Country], [Total Orders], [Total Items Ordered] <br />-- Should clean up afterwards<br />drop table #C_Totals<br />
  10. 10. This is the data flow and control flow for the Job Time Sheets package. This package imports multiple csv files doing checks to insure data integrity and writing rows that fail to an error log file for review. This is just one part of a project that brought in the employee and customer data of a construction company. The data structure created here was used in several subsequent BI projects.<br />
  11. 11. This is the script that tracks how many records were processed for the Job Time Sheets package. It breaks them up into Inserted, Updated and Error categories. These totals are used in the email that is sent when processing is completed.<br />&apos; Microsoft SQL Server Integration Services Script Task<br />&apos; Write scripts using Microsoft Visual Basic<br />&apos; The ScriptMain class is the entry point of the Script Task.<br />Imports System<br />Imports System.Data<br />Imports System.Math<br />Imports Microsoft.SqlServer.Dts.Runtime<br />Public Class ScriptMain<br />Public Sub Main()<br /> Dim InsertedRows As Integer = CInt(Dts.Variables(&quot;InsertedRows&quot;).Value)<br /> Dim ErrorRows As Integer = CInt(Dts.Variables(&quot;ErrorRows&quot;).Value)<br /> Dim RawDataRows As Integer = CInt(Dts.Variables(&quot;RawDataRows&quot;).Value)<br /> Dim UpdatedRows As Integer = CInt(Dts.Variables(&quot;UpdatedRows&quot;).Value)<br /> Dim InsertedRows_fel As Integer = CInt(Dts.Variables(&quot;InsertedRows_fel&quot;).Value)<br /> Dim ErrorRows_fel As Integer = CInt(Dts.Variables(&quot;ErrorRows_fel&quot;).Value)<br /> Dim RawDataRows_fel As Integer = CInt(Dts.Variables(&quot;RawDataRows_fel&quot;).Value)<br /> Dim UpdatedRows_fel As Integer = CInt(Dts.Variables(&quot;UpdatedRows_fel&quot;).Value)<br />Dts.Variables(&quot;InsertedRows&quot;).Value = InsertedRows + InsertedRows_fel<br />Dts.Variables(&quot;ErrorRows&quot;).Value = ErrorRows + ErrorRows_fel<br />Dts.Variables(&quot;RawDataRows&quot;).Value = RawDataRows + RawDataRows_fel<br />Dts.Variables(&quot;UpdatedRows&quot;).Value = UpdatedRows + UpdatedRows_fel<br />Dts.TaskResult = Dts.Results.Success<br /> End Sub<br />End Class<br />
  12. 12. This is the data flow of a package that merged data from multiple tables together in order to create a fact table for a cube. This fact table was the key fact table used in the final BI project for our class.<br />
  14. 14. This section uses the staging area that was created in the SSIS section. Here the data is deployed from the staging area into a cube and SSAS is used to create KPIs and Excel Reports.The AllWorks database deployed as a cube using SSAS<br />
  15. 15. Browsing the AllWorks data cube to make sure the data is organized in the desired manner for purposes in which it will be used.<br />
  16. 16. Creating Calculated Members for use in KPIs and Excel Reports<br />
  17. 17. Creating Key Performance Indicators (KPIs) to show visually goals, trends and changes in tracked metrics<br />
  18. 18. Use of a KPI in Excel to show Profits against projected goals.<br />
  19. 19. Partitioning the cube to separate archival data from more frequently accessed data. Also Aggregations were setup here to further enhance storage and query performance.<br />
  20. 20. MDX PROGRAMMING<br />
  21. 21. This section uses the AllWorks cube created in the last section. The code created here was used in created calculations for use in KPIS.For 2005, show the job and the top three employees who worked the most hours. Show the jobs in job order, and within the job show the employees in hours worked order<br />SELECT<br />[Measures].[Hoursworked]<br />ON COLUMNS,<br />non empty <br />Order(Generate([Job Master].[Description].[Description].members,<br /> ([Job Master].[Description].currentmember,<br /> TOPCOUNT([Employees].[Full Name].[Full Name].members,<br /> 3,[Measures].[Hoursworked]))),<br /> [Measures].[Hoursworked],DESC)<br />on rows<br />FROM Allworks<br />WHERE[All Works Calendar].[Fy Year].&[2005] <br />
  22. 22. Show Overhead by Overhead Category for currently selected quarter and the previous quarter, and also show the % of change between the two. <br />WITH<br />MEMBER [Measures].[Previous Qtr] AS<br /> ([Measures].[Weekly Over Head],<br />ParallelPeriod ([All Works Calendar].[Fy Year - Fy Qtr].level<br /> ,1,[All Works Calendar].[Fy Year - Fy Qtr].currentmember) )<br /> ,FORMAT_STRING = &apos;$#,##0.00;;;0‘<br />MEMBER [Measures].[Current Qtr] AS<br /> ([Measures].[Weekly Over Head],<br /> [All Works Calendar].[Fy Year - Fy Qtr].currentmember)<br /> ,FORMAT_STRING = &apos;$#,##0.00;;;0‘<br />MEMBER [Measures].[% Change] AS<br />iif([Measures].[Previous Qtr], <br /> (([Measures].[Current Qtr] - [Measures].[Previous Qtr]) <br /> / [Measures].[Previous Qtr]),NULL),<br /> FORMAT_STRING = &apos;0.00%;;;N/A‘<br />SELECT<br />{[Measures].[Current Qtr], <br />[Measures].[Previous Qtr], <br />[Measures].[% Change]}<br />on columns,<br />non empty [Overhead].[Description].members<br />on rows<br />FROM Allworks<br />WHERE [All Works Calendar].[Fy Year - Fy Qtr].[2005].lastchild<br />
  23. 23. List Hours Worked and Total Labor for each employee for 2005, along with the labor rate (Total labor / Hours worked). Sort the employees by labor rate descending, to see the employees with the highest labor rate at the top. <br />WITH<br />MEMBER [Measures].[Labor Rate] AS<br />[Measures].[Total Labor]/[Measures].[Hoursworked],<br />FORMAT_STRING = &apos;Currency&apos;<br />SELECT<br />{[Measures].[Hoursworked],[Measures].[Total Labor],<br />[Measures].[Labor Rate]}<br />ON COLUMNS,<br />non empty Order([Employees].[Full Name].members,<br />[Measures].[Labor Rate], BDESC)<br />on rows<br />FROM Allworks<br />WHERE[All Works Calendar].[Fy Year].&[2005]<br />
  25. 25. This report uses the AllWorks cube and shows an employees labor cost by weekending date with a grand total at the bottom. Cascading parameters are used to select the employee and dates.<br />
  26. 26. A report of region sales percentage by category for a selected year.<br />
  28. 28. A breakdown of the labor cost of an employee by quarter. The line graph shows the percentage of labor of the employee for the quarter. The chart at the bottom shows the breakdown by job. These use the AllWorks cube created earlier.<br />
  29. 29. The custom MDX code that allows the previous report to run<br />
  30. 30. This scorecard has a drill down capability that will allow you to see regions, states and city Sales goals. In addition it is hot linked to a report that shows Dollar Sales.<br />
  31. 31. MS OFFICE EXCEL SEVICES 2007<br />
  32. 32. This excel spreadsheet has taken data from a cube and created a chart. This chart and its parameter will then be published using Excel Services to make it available on a Sharepoint server.<br />
  33. 33. Another chart built using Excel with data from a cube. This chart allows the tracking of sales data by Category on a selected year. In addition it tracks the selected category percentage of sales vs. the parent on a separate axis. This chart with its parameters was published to SharePoint Server using Excel Services.<br />
  35. 35. SharePoint site created with document folders to hold Excel spreadsheets published with Excel Services, SSRS reports, and Performance Point Dashboards. Two web parts are on the front page showing a Excel chart and SSAS KPI published through Performance Point.<br />
  36. 36. The previously shown Employee Labor Analysis Report deployed to SharePoiont as part of A Performance Point Dashboard.<br />
  37. 37. An SSRS reported scheduled to be autogenerated using SharePoint scheduling and subsription services<br />
  38. 38. Excel spreadsheets and charts deployed to SharePoint using Excel Services.<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.