This document provides an overview and samples of a business intelligence project using SQL Server Integration Services (SSIS), SQL Server Analysis Services (SSAS), and SQL Server Reporting Services (SSRS). It includes descriptions of ETL packages in SSIS to load and transform data, a cube with dimensions and calculations in SSAS, and sample MDX queries and reports. The goals are to track, analyze, and report on facets of a simulated construction company.

2. Table of Contents SetFocus Business Intelligence Masters Program Project 3 SQL Server Integration Services 4 Sample Documentation for SSIS portion 5 Master Package 6 Employee Master Package Control Flow 8 Employee Master Package Data Flow 9 Project Time Sheets Package Control Flow 10 Project Time Sheets Package Data Flow 12 SQL Server Analysis Services 13 Data Source View 14 The Cube’s Dimensional Usage 15 The Cube’s Calculated Members 16 The Cube’s KPIs 17 Sample Grouping One with SA Query Results in Excel 18 Sample Grouping Two with SA Query Results in Excel 19 Sample One MDX Queries with Results in Management Studio 20 Sample Two MDX Queries with Results in Management Studio 21 Sample Three MDX Queries with Results in Management Studio 22

3. SetFocus Business Intelligence Masters Program Project Core technologies used in the program: Microsoft SQL Server 2005 Microsoft SQL Server 2005 Integration Services (SSIS) Microsoft SQL Server 2005 Analysis Services (SSAS) Microsoft SQL Server 2005 Reporting Services (SSRS) Microsoft Office SharePoint Server 2007 (MOSS) Microsoft Office Performance Point Server Project Summary Design and build a Business Intelligence solution for a simulated construction company in order to track, analyze and report on every facet of the companies business. Project Goals Using SSIS, build an ETL solution to update the SQL Server 2005 database on a nightly basis from Excel and other flat file sources. Using SSAS, create a cube, with partial snowflake architecture. Implement a variety of MDX queries in order to manipulate and analyze the data in the cube. Using SSAS implement various calculations in order to built critical Key Performance Indicators(KPIs). Using SSRS, produce various detailed summary reports. Using MS Office PerformancePoint Server, produce various dashboards containing scorecards, KPIs and summary reports. Using MS Office SharePoint Server, setup Site Collection to receive report and a dashboard with web parts.

4. SQL Server Integration Services Overview of Goals for SSIS portion: Create a data source using either the XML or System.Data.ODBC drivers Create packages to read each source file and insert/update into AllWorksDBStudent SQL Database. Remember that the structures may be different for each set of files Generate an email to report the results of every package, including rows inserted and any errors generated (for example, timesheet records may contain invalid foreign keys). All scheduled packages will run nightly at midnight. Create a separate package to handle nightly database backups. All backups should occur nightly, after the last transfer of source data. After the backup occurs, create another package to reindex all files and shrink the database.

5. Sample Documentation for SSIS Portion Package 3a: EmployeeMasterPackage.dtsx Source File: C:\SetFocusBIProjects\StudentVersion\SSISStudentProject\Employees.xls Sheet: Employees Target Table: AllWorksDBStudent.dbo.Employees Log file and Log Table: C:\SetFocusBIProjects\StudentVersion\SSISStudentProject\Logs\EmployeesErrorLog.csv Assumption: Per instructor, data load file will not contain records with NULL key values and also the initial data load will not contain any duplicate keys. Notification includes the following information: Successful email notification will include the following: Total number of rows in the source file Total number of new rows inserted Total number of existing rows updated Total number of error rows Error Handling: One File is generated for all error logging. The log file is then attached and sent in an email containing package execution statistical results.

6. Master Package At midnight every day the Master Package runs all the other packages contained in the ETL container. The ETL container has execute package tasks; each package is deployed to the SSIS stored packages. Upon completion it launches the Maintenance container comprising of a Back-up, Rebuild Index and Shrink database tasks. Separate failure notices are email if either container fails and separate progress email are sent when each container succeeds.

7. Master Package The ETL container has execute package tasks; each package has been deployed to the SSIS stored packages area of the server.

8. Employee Master Package Control Flow This package populates or updated a SQL Server table and notified the relevant parties whether it was successful in its tasks. Conditional record counts are captured by variables used to construct the email message reporting Error rows, New Rows and Updated rows if the package is successful. If the package fails then an email is sent reporting that this package failed.

9. Employee Master Package Data Flow The data is imported from an Excel Source, record count is captured by RawDataRows variable, converted to DB data types, columns combined to create FullName, EmployeeID looked-up to find matching records and then split. In order of condition evaluation: Records containing any null attribute values are routed as Error, record count is captured by ErrorRows variable and exported to a flat file error log. Records with EmployeeID that do not match in existing staging table are routed as New, record count is captured by InsertedRows variable and inserted into staging table. Records with matching EmployeeID are routed as Changed, record count is captured by UpdatedRows variable and all attributes are updated in staging table.

10. Project Time Sheets Package Control Flow This package reads multiple CSV files in a controlled folder and populates the JobTimeSheets table in the ETL staging area on the server, then summarizes all the rows counts captured by the variables using a VB script, creating a new set of row count variables for cumulative totals for all sheets processed in that package execution. Summary rows counts are composed into a message/progress report and emailed with attached error log.

11. Project Time Sheets Package Control Flow The Script Editor properties show the incoming read only parameters and the outgoing parameters with cumulative total rows counts. This is the VB code used to calculate cumulative totals for each type of rows count. These calculations are performed with each loop through individual employee time data sheet contained in the time folder. Final tallies are emailed in progress report. Public Sub Main() Dim InsertedRows As Integer = CInt (Dts.Variables( "InsertedRows" ).Value) Dim ErrorRows As Integer = CInt (Dts.Variables( "ErrorRows" ).Value) Dim RawDataRows As Integer = CInt (Dts.Variables( "RawDataRows" ).Value) Dim UpdatedRows As Integer = CInt (Dts.Variables( "UpdatedRows" ).Value) Dim InsertedRows_fel As Integer = CInt (Dts.Variables( "InsertedRows_fel" ).Value) Dim ErrorRows_fel As Integer = CInt (Dts.Variables( "ErrorRows_fel" ).Value) Dim RawDataRows_fel As Integer = CInt (Dts.Variables( "RawDataRows_fel" ).Value) Dim UpdatedRows_fel As Integer = CInt (Dts.Variables( "UpdatedRows_fel" ).Value) Dts.Variables( "InsertedRows" ).Value = InsertedRows + InsertedRows_fel Dts.Variables( "ErrorRows" ).Value = ErrorRows + ErrorRows_fel Dts.Variables( "RawDataRows" ).Value = RawDataRows + RawDataRows_fel Dts.Variables( "UpdatedRows" ).Value = UpdatedRows + UpdatedRows_fel Dts.TaskResult = Dts.Results.Success End Sub End Class

12. Project Time Sheets Package Data Flow Like the previous package this package also imports, converts, counts, matches FKs to the existing staging tables (Employees, JobMaster & JobTimeSheets). The data is also checked for missing information and logged. Error logic is: ISNULL(ConvertedEmployeeID) || ISNULL(ConvertedWorkDate) || ISNULL(ConvertedJobNumber) || ISNULL(ConvertedRegHours) || ISNULL(MatchedEmployeesEmployeePK) || ISNULL(MatchedJobMasterJobMasterPK) || (MatchedJobMasterJobClosed == TRUE && MatchedJobMasterJobClosedDate < ConvertedWorkDate)

13. SQL Server Analysis Services Overview of Goals for SSAS portion There are three phases to the SSAS Project: Based on a family of stars schema model I created a SSAS solution in BIDS, and built four fact tables in the cube Built 5 KPIs in the cube and demonstrated functionality via Excel SSAS query I produced a broad sample of MDX queries against the cube to demonstrate my skill-set and test the cube

14. Data Source View This DSV was created in BIDS, it shows the 4 fact tables

15. The Cube’s Dimensional Usage

16. The Cube’s Calculated Members

17. The Cube’s KPIs

18. Sample Grouping One with SA Query Results in Excel

19. Sample Grouping Two with SA Query Results in Excel

20. Sample One MDX Query with Results

21. Sample Two MDX Query with Results

22. Sample Three MDX Query with Results