1. BI on a Dime OR HOW I LEARNED TO STOP WORRYING AND LOVE BI

2. Agenda  Get up to speed on terms  Feather River College case  See business intelligence in action  Strategy – Architecture – Infrastructure  Data Warehouse ERD Exercise

3. What are we talking about?  Business Analytics: is the extensive use of data, statistical and quantitative analysis, explanatory and predictive models, and fact-based management to drive decisions and actions.  Business Intelligence (BI): A set of technologies and processes that use data to understand and analyze business performance. BI includes both data access and reporting, and analytics.

4. What are we talking about?

5. Last slide on this, I promise!  Transaction Database: A system designed to process transaction data. Optimized for putting data into the system quickly.  Data Warehouse: A system designed to store validated data for the long haul. Optimized for fast querying.  Data Mart: A user interface to present data. Should be designed to be intuitive.

6. FRC Case  First: Where the hell is Feather River College?

7. FRC Case  The Problem: The institution had matured to the point that it was good at putting data into the ERP system – Banner. Unfortunately we weren’t any good at getting it out.  Limited resources:  Staff  Money  Technical Expertise

8. FRC Design and Implementation  Sample – Data Flow Diagram Data Flow Diagram

9. FRC Design and Implementation  SQL Server - Parts SSIS Analysis Services Reporting Services Manage- ment Studio

10. FRC Design and Implementation  It’s Demo Time  Finished Examples

11. A QUICK Lesson in Database Design  Databases power this stuff so you should learn about how to design them  Scenario: You want to track which employees are on committees and when they joined or left the committee. EmployeeID FirstName LastName Committee WhenStarted WhenLeft EmployeeIDFirstNameLastNameCommitteeWhenStartedWhenLeft 12345BrianMurphySLOAC4/1/2010 12345BrianMurphySEM4/1/20104/1/2014 12345BrianMurphySPC4/1/2010

12. A QUICK Lesson in Database Design  Start breaking data out by dependency  Look at relationships *EmployeeID FirstName LastName Employee *CommitteeID CommitteeName Committee ?

13. A QUICK Lesson in Database Design  Because employees can serve on multiple committees and committees have multiple employees on them, we need an linking table. *EmployeeID FirstName LastName Employee *CommitteeID CommitteeName Committee * EmployeeID *CommitteeID StartDay EndDay EmployeeCommitte

14. FRC Design and Implementation  It’s Demo Time - Making Sausage  FRC ERD  FRC SQL Server Stuff

15. Ideas for Development Remember the audience  Different data marts for different folks  Understand at a glance  Simplify  You still have IR to take care of the hard stuff  Train

16. Ideas for Development Fast, Inexpensive, Always improving, Always on

17. Ideas for Development Minimum Information System Requirements  SQL Server 2012 (Enterprise Edition)  Adequate ram very important  SharePoint 2010 (Enterprise Edition)  Running on SQL Server 2012 platform  Silverlight installed on clients  Communication between servers  Administrative rights on SQL Server

18. Ideas for Development Future Compliant Information System Requirements  SQL Server 2012 (Enterprise Edition)  Adequate ram very important  SharePoint 2013 (Enterprise Edition or adequate Office 365 version)  Running on SQL Server 2012 platform  Office 2013  Communication between servers  Administrative rights on SQL Server

19. Ideas for Development  Suggested Reading  Murach’s SQL Server 2012 for Developers  Delivering Business Intelligence with Microsoft SQL Server  Competing on Analytics

20. Wrap Up Thank you!