Agile bi u sing microsoft sql server 2012
Download
1 / 16

Agile BI u sing Microsoft SQL Server 2012 - PowerPoint PPT Presentation


  • 125 Views
  • Uploaded on

Agile BI u sing Microsoft SQL Server 2012. Neelesh Raheja VP Consulting Services, GNet Group [email protected] @ PracticalBI. Agenda. Level set on components of a BI solution The Microwave S ociety – Speed Evolution & Change Approaches to BI Classic Agile

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Agile BI u sing Microsoft SQL Server 2012' - komala


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Agile bi u sing microsoft sql server 2012

Agile BI using Microsoft SQL Server 2012

Neelesh Raheja

VP Consulting Services, GNet Group

[email protected]

@PracticalBI


Agenda
Agenda

  • Level set on components of a BI solution

  • The Microwave Society – Speed

  • Evolution & Change

  • Approaches to BI

    • Classic

    • Agile

    • Blend of both approaches

  • Agility with Microsoft SQL Server 2012

    • 2 Scenario’s

    • In Summary

    • Q&A


Level set food for thought
Level Set – food for thought

  • Components of a BI solution?

    • ETL (Extract, Transform, Cleanse, Load)

    • Data Warehouse (includes ODS, Staging, Dim Model)

    • Presentation (OLAP, Reports, Dashboards etc)

  • Which of the above 3 can we get rid off and still deliver a long term & robust Ent. BI solution?

  • None! Enterprise Data Integration & Architecture is key to a successful Enterprise BI Solution


The microwave society
The Microwave Society

  • Pace of business and short attention span

  • Exponential growth in data, sources and reporting needs

  • Reduced cycle times and pressure to react faster

  • Need to deliver on reporting needs today

  • The next business question is already here!

Can we deliver an Enterprise BI Solution….tomorrow? Next Week? Next Month?


Bi solutions must and will evolve
BI solutions must and will evolve

Changes in DW

Challenges

Ent Data Architecture

Time

Transparency: Report what happened? (DW and Reports)

Improvements

Measure change impact

(Evolve DW, Dsh, Rpts)

Discover & Question what’s happening?

(Dashboards and Ad-Hoc Analysis)

Processes & Data

Changes

What should happen?

(Goal and process)

Understand Why? Cause & Effect?

(root cause & predictive analytics)


Classic approach to bi
Classic approach to BI

  • Ent Data Integration & Architecture

80%-Backend work

Takes too long

  • Time

20%-Touch and feel at project end

  • How often do requirements evolve during design/development?

  • How often do requirements change and impact design/development?

  • How often are the requirements and data in sync?

  • How does the above impact design/development?

  • How fast can we change a DW / ETL to align with changing requirements?


Agile approach to bi
Agile approach to BI

  • Ent. Data Integration & Architecture

  • Time

  • What about data integration i.e. Ent Data Warehouse? One EDW vs. siloed Data Marts

  • What about multiple perspectives of data (e.g. sales hierarchy, marketing hierarchy)?

  • What about single source of truth? (e.g. Multiple Data marts – sales, marketing)

  • Can we rebuild / change data marts without impacting reports?

  • How can we build a single, consistent enterprise data warehouse over time?


Blend the two

10A. Deployment

Blend the two?

9A. Development

2. Assessment, Roadmap and Release Plan

1. Business Vision and Strategy

8A. Physical Design

7A. Physical Design

For Each Roadmap Phase

6A. Build ODS /Dimensional Model Based on Personal / Team

Data Warehouse build In parallel

  • Ent Data Architecture

  • Time: Early Results. Buy Time for Data Architecture

  • End Goal is a comprehensive BI solution (ETL, EDW and Presentation)

  • Agile BI Solutions in the interim while Data Architecture is built

  • Ent. Data Architecture: ODS, EDW based on Exploration, Evaluation and Evolution.

  • Accelerate robust EDW build based on solid requirements and feedback


How does sql 2012 fit in

10A. Deployment

How Does SQL 2012 fit in?

9A. Development

2. Assessment, Roadmap and Release Plan

1. Business Vision and Strategy

8A. Physical Design

7A. Physical Design

For Each Roadmap Phase

1st Iteration - PowrerPivot

2nd Iteration Team BI with SharePoint & PowerPivot or Org BI - SSAS

6A. Build ODS /Dimensional Model Based on Personal / Team

Data Warehouse build In parallel

  • Ent Data Architecture

  • Time: Early Results. Buy Time for Data Architecture

  • Time : Agile, self service personal (PowerPivot) and/or team BI (PowerPivot for SharePoint)

  • Promote PowerPivot to SSAS (Org BI)

  • Some applications will remain in PowerPivot (Personal / Team)


New in sql 2012 analysis services bi semantic model
New in SQL 2012 Analysis Services:BI Semantic Model

BI Semantic Model

One Model for all End User Experiences

Data model

Client ToolsAnalytics, Reports, Scorecards,

Dashboards, Custom Apps

Business logic

and queries

Data access

Team BI

Personal BI

Organizational BI

Analysis Services

PowerPivot for SharePoint

PowerPivot for Excel

Data Sources

Databases, LOB Applications, Data Feeds,

Spreadsheets, Text Files


Scenario 1 first dw end goal is edw
Scenario 1: First DW (end goal is EDW)

2

Organizational BI

Personal BI

Team BI

CRM

Power Pivot for SharePoint

PowerPivot

Power Pivot for Excel

Performance Point

Excel and Excel Services

SSRS

Promote to IT Managed Environment – Process & Security

ERP

BI Semantic Model

1

POS

3

EDW

Analysis Services

Other

ODS

POS

Other

CRM

ERP

Agility and long term data architecture!

SOURCE DBs


Scenario 2 additions to existing dw
Scenario 2: Additions to existing DW

2

Organizational BI

Personal BI

Team BI

CRM

Power Pivot for SharePoint

PowerPivot

Power Pivot for Excel

Excel and Excel Services

Performance Point

SSRS

Promote to IT Managed Environment – Process & Security

ERP

BI Semantic Model

1

POS

EDW

Analysis Services

Other

ODS

POS

Other

CRM

ERP

Agility and long term data architecture!

SOURCE DBs


Evidence of the blended approach
Evidence of the blended approach

  • Pentair Technical Products – Price Realization Project


Benefits
Benefits

  • Blended approach addresses both Data Architecture and the Need for Speed

  • Prototyping

  • Visualizing, touching, feeling the data – facilitates discovery and exploration

  • Enables data profiling, validate requirements

  • Keeps customers engaged and involved in the process

  • Focus is on business discussion vs technical specifications

  • Facilitates ownership and adoption

  • Classic Approach based on feedback

  • Accelerates Data Architecture (EDW) build in parallel based on solid requirement

  • Perception of speed, they see activity, no big gaps in time, “pressure relief valve”

  • Removes the unknown which results in uncertainty and a sense of risk

  • Reduces cost of Data Architecture build

  • Leadership can see the value in action


In summary
In Summary

  • Need to blend Agile and Classic approach

  • Why PowerPivot?

    • Modeling and building the solution at the same time

    • Can promote model/solution to enterprise class BI Solution

  • This approach does not eliminate

    • EDW. Changes how we approach data architecture and time

    • Biz/IT engagement. Partnership is still key

    • Roadmap and periodic (90 days) refactoring / re-prioritization

  • Must

    • Enable self service to accelerate results and adoption

    • Incorporate prototyping & deploy to production–Touch & Feel asap!

    • Gather feedback for long term data architecture

    • Execute on it too! EDW is a must

  • Technical Architecture for SQL Server 2012 in memory technologies

  • Yes! Training and hands-on experience with 2012


Thank you
Thank You

For more information contact

NeeleshRaheja

VP Consulting Services, Gnet Group

[email protected]

@PracticalBI


ad