8. What’s Business Intelligence (BI)? Business intelligence (BI) is more of a concept than a single technology. The goal is to gain insight into the business by bringing together data, formatting it in a way that enables better analysis, and then providing tools that give users power—not just to examine and explore the data, but to quickly understand it. The above definition from Business Intelligence with Microsoft Office PerformancePoint Server 2007
9.
10. Why Business Intelligence? Poor Visibility and Reaction to Market Events High Business and IT Operation Costs Poor Understanding of Customer Needs Inefficient Supply Chains and Demand Chains Poor Business Performance Management by Spreadsheets Data Privacy Concerns and Information Overload Compliance (BASEL, Sarbanes Oxley) Today’s information TECHNOLOGY 80% of IS Budget to ‘business as usual’
11.
12.
13.
14. MS-SQL SERVER 2005 BI Refer from: http :// www . renaissance . co . il / ivbug / meeting74 / SQL%20Server2005%204%20VB%20group . ppt Analysis Services OLAP & Data Mining Data Transformation Services SQL Server Relational Engine Reporting Services Management Tools Development Tools
15. BI vs Users Analysts Information Consumers Information Explorers 5-10% of users 15-25% of users 65-80% of users Reporting Services Analysis Services
16. Microsoft BI Components SQL Server 2005 Management Studio SQL Server 2000 Enterprise Manager, Analysis Manager Database Management Tools SQL Server 2005 Business Intelligence Development Studio SQL Server 2000 Enterprise Manager, Analysis Manager, Query Manager… Database Development Tools SQL Server 2005 Report Builder Business Scorecard Manager Microsoft Office Products Microsoft Office Products Ad hoc Query and Analysis SQL Server 2005 Reporting Services SQL Server 2000 Reporting Services Managed Reporting SQL Server 2005 Analysis Services SQL Server 2000 Analysis Services Data Mining SQL Server 2005 Analysis Services SQL Server 2000 Analysis Services Multidimensional Database SQL relational database SQL relational database Relational Data Warehouse SQL Server 2005 Integration Services SQL Server 2000 Data Transformation Services (DTS) Extraction, Transformation and Loading SQL Server 2005 SQL Server 2000 Component
17.
18. Information Delivery Data Marts Data Analysis (OLAP, Data Mining) Familiar, Powerful BI Tools Client Portal Devices Enterprise ETL Third Party Applications Enterprise Reporting Performance Scorecard Interactive Reports Business Insights Data Warehouse Highly intuitive, visual tools…greater productivity from developers to users Comprehensive ability to integrate any data… improved data completeness CRM LOB ERP Source Systems Tightly integrated “all-in-one” technology solution… increased manageability and the best economics
27. Demo Import & Export Wizard New DB (1) Start on New DB (2) Selected Data Source (Input) Select “AdventureWorks” (3) Selected Destination (Output) Default destination is selected DB
29. Demo Import & Export Wizard (Cont’) (7) Save & Excuse (8) Confirm before start (9) Result Status
30.
31. Demo: Creating A Package (1) Click here (2) File New Project… (3) BI Projects Integration Services Project Selected Here
32.
33.
34.
35. Demo for Connection Manager 1) Right click in this area 2) Select OLE DB Connection 3) Show Existing Connection 4) Create new connection 5) Select SQL Native Client provider 6) Configuration for link to new DB 6) Test Connection for confirm
36. Demo for Connection Manager 7) Finally, we get new connection. Select and press OK 8) Then, we get new connection 9) Create New data source is “ Flat File ” (we use department.txt for sample) 11) Select department.txt (sample) 12) Check it! 10) Input name & information
37. Demo for Connection Manager 13) Click on Column 14) Verify data in text file 15) Click on Advance icon for go to Advance Page
38. Demo for Connection Manager 16) Click on New button 17) Display new column 18) Change column name to DepartmentName 19) Click on OK button 20) New Connection appear
39. Demo for Connection Manager 21) Right-Click on DepartmentList (new Connection) 23) Select on new connection and check in Properties panel 22) Select copy & paste on connection manager 24) Change values: - Change the Name property to DepartmentListBackup . Change the ConnectionString property to C:epartmentsBackup.txt . 25) Finally, we get..
40.
41.
42.
43.
44. Demo for Building Control Flow 1) Pin the tool bar 2) Select File System Task 3) Drag to area of Control Flow 4) Drag to area of Control Flow 5) Make Green arrow connect
45. Demo for Building Control Flow 6) Double-click on link. 7) Change the Value from Success to Completion, because you want the Data Flow Task to execute whether the File System Task succeeds or not. 8) Click OK
46. Demo for Building Control Flow 9) Double-Click on this task 10) Change Property Set the Source property to DepartmentList. Set the Destination property to DepartmentListBackup. Set the OverwriteDestinationFile property to True. 11) Click on OK button
47. Demo for Building Control Flow 12) Run it!!! All are Green! But it’s warning in output dialog Overall status Check result in folder, new file has created!
48.
49.
50.
51.
52. Demo for Building the Data Flows 1) Select Data Flow tab 2) Select Data Flow task 3) Drag & Drop OLE Source 4) Drag & Drop Character Map 5) Drag & Drop File Destination 6) Drag green Arrow to below box
53. Demo for Building the Data Flows 7) Double-click on OLEDB source 8) Select table/views: HumanResources.Department 9) Click on OK button
54. Demo for Building the Data Flows 10) Double-click on Character Map 11) Select Name column 12) Change to in-place change 13) Change to Upper Case Then press OK button
55. Demo for Building the Data Flows 14) Double-click on Flat File Destination 15) Select the DepartmentList Flat File Connection Manager 16) Drag Name column to DepartmentName column Then press OK button
56. Demo for Building the Data Flows 17) Run it!!! All are Green! Overall status Result: transform one of the columns in that table to all uppercase characters, and then write that transformed column out to a flat file.
57.
58.
59. Demo for Creating Event Handlers 1) Click on Execute SQL task 2) Drag and drop in this area 3) Double-click on this object 4) Change ConnectType = OLEDB 5) Select OLEDB connection 6) Input SQL statement INSERT INTO DepartmentExports (ExportTime) VALUES (GETDATE()) 7) Click on OK button
60. Demo for Creating Event Handlers 8) Run it!!! (Please delete the existing files and use original files before run) All are Green! Overall status Check result after running the package
61. Execution Results (in BIDS) See Progress tab (after running) Progress is OK Warning message
62.
63.
64. Demo for Saving Packages (1) Save current package as… (2) Input information as below picture: (3) Specifield path as /File System/ExportDepartments (4) Click on OK button
65. Demo for Running Packages (1) Select Connect Integration Services (2) Input login information and press Connect. (3) Expand & Find store package (4) Select Run Package
66. Demo for Running Packages (5) Click on Execute (6) Display result on pop-up window
72. Analysis Services High-level Architecture Dashboards Rich Reports BI Front Ends Spreadsheets Ad Hoc Reports Analysis Services Cache SQL Server Teradata Oracle DB2 LOB DW Datamart XML/A or ODBO UDM
73.
74.
75.
76.
77.
78. Creating a Data Cube (1) File New Project… (2) Select “Analysis Services Project”
79. Creating a Data Cube (3) From new solution, right click on Data Sources (4) Create New Connection for AdventureWorksDW (5) Select Default impersonation information to use the credentials you just supplied for the connection and click Next.
80. Create Data Source View (1) From new solution, right click on Data Sources View (3) Assign Name “Finance” and click on Finish (2) Select Data Source Select Tables
81.
82. Invoking the Cube Wizard (2) Select option as shown in below pictures and click Next button (1) Right-Click on Cubs New Cube… (3) Select Data source and click Next
83. Invoking the Cube Wizard (4) Wait until Cube Processing finish, then click on Next button (5) Identify Dimension & Fact Select table “DimTime” Select Fact & Dimension table (as shown in picture) Click on Next button
84. Invoking the Cube Wizard (6) Select Time Periods (7) Accept default measure (8) Wait until Cube Wizard detected hierarchy Click on Next button
85. Invoking the Cube Wizard (9) Accept default Dimension (10) Assign Cube Name Click on Finish button
86. Deploying and Processing a Cube (1) Build Deploy (2) Waiting while processing One of the tradeoffs of cubes is that SQL Server does not attempt to keep your OLAP cube data synchronized with the OLTP data that serves as its source. As you add, remove, and update rows in the underlying OLTP database, the cube will get out of date. Re-Run Process
87.
88. Exploring a Data Cube Drag into Total/Detail Area Drag into Row Field Area Define hierachy from Dim Time Calendar Year-Calendar Quarter-Month Number of Year Filter Area: Scenario Name
89.
90. References/External Links (1) SSIS Tutorial: SQL Server 2005 Integration Services Tutorial http:// www.accelebrate.com/sql_training/ssis_tutorial.htm (2) SSAS Tutorial: SQL Server 2005 Analysis Services Tutorial http:// www.accelebrate.com/sql_training/ssas_tutorial.htm (3) MS SQL Server Data Transformation Services & Integration Services Chris Riley March 29, 2007 (4) Intro to SQL Server Integration Services & SQL Agent Jobs Stu Yarfitz Analyst/Programmer, Collaborative Data Services. FHCRC 6/18/2008
91. Thank you for your attention! [email_address] www.blueballgroup.com
Editor's Notes
The Analysis Services technology remains at the heart of Microsoft’s BI capabilities. It is now in its third generation and has delivered a wide set of new options – both functional & management/scalability focused. We’ll focus on three key areas: The UDM – a new approach to modeling the inputs to the OLAP capabilities of SQL Server Analysis Services that can help eliminate costly data staging areas and business-function specific data marts KPI – a new architecture for delivering goal-based metrics to the organization Deep Data Mining – moving beyond slice & dice and drilldown to provide tools that help you catch complex relationships and patterns in your data and predict outcomes based on past results.
ODBO = OLEdb for OLAP XMLA = XML for Analysis
UDM: SQL Server 2005 introduces the Universal Data Model – this technology provides the mechanism to describe data sources in a BI-friendly manner without requiring changes to the source data. This can eliminate the need for staging areas as data can be consumed directly from the source systems. The models can then be used to drive multiple cubes (or live caches of the underlying data). By looking at the cubes as a series of high-performance caches the best of the OLAP & OLTP worlds can be combined. Cache: The cache is a MOLAP datastore that manages the retrieval of data from backend data sources. You can control how frequently the multidimensional cache is rebuilt, if stale data can be queried while the cache is being refreshed, and whether data is retrieved to a schedule or when it changes in the database. Business Intelligence Smarts: SQL Server 2000 included time dimension awareness – this is extended in SQL Server 2005 to cover autogeneration of several key calculations that really help you to jumpstart any BI system: Time – adds the following calculations: Period to date, Period over period growth, Moving average and Parallel period comparisons. Accounting – cost, balance & other accounting calculations Dimension – choose from a list of known dimension types and also automatically set additional attributes to autogenerate appropriate calculations Set your own aggregation operator or calculation and control updateability Data Mining: We’ll cover more on this later XMLA: SQL Server 2005 implements the open standard: XML for Analysis – optimized for scalable web access to access & define OLAP data.
