This document provides an overview and update of Microsoft's Cloud Business Intelligence (BI) solutions in version 3.0 from June 2012. It discusses the objectives of Cloud BI including providing data access and answers to business questions anytime from mobile devices. An overview of the session covers Windows Azure, SQL Azure, SQL Azure Reporting Services, mobile BI delivery, cloud data integration, data mining in the cloud, and hybrid scenarios. Key features of SQL Azure like import/export, data-tier applications, data sync, and federations for database scale-out are also summarized.
3. Objectives of Cloud BI
• Provide quick, easy data access to business decision makers
• Provide answers to complex business questions anytime, anywhere
• Promote use of empirical data to improve business decision making
• Monetize business data to outside customers and partners
• Enable mobile users outside of firewall
• Cloud Computing Value Prop
– Lower infrastructure costs
– Quick time to production
– Fast & easy scale
4. Overview of Session
• Windows Azure
• SQL Azure
• SQL Azure Reporting Services
• Mobile BI Delivery
• Cloud Data Integration
• Data Mining in the Cloud
• Hybrid Scenarios
6. SQL Azure Database
Single Logical Multiple Physical
Database Replicas
Replica 1
Replica 2
D
B
Replica 3
• Reads are completed at the primary
• Writes are replicated to a quorum of
secondaries
7. SQL Azure Key Features
Import/Export (Backup/Restore)
Data-Tier Applications (DACPAC)
Data Sync (Replication)
Federations (Database Scale-out Sharding)
9. Tools Symmetry
• SQL Server Management Studio
• DACPAC – deploy/upgrade & extract with
.dacpac packages
• BACPAC – import/export to Azure blob store
or file system with .bacpac packages
• SQL Azure Management Portal
• DACPAC – deploy/upgrade & extract with
.dacpac packages
• BACPAC - import/export to Azure blob store
with .bacpac packages
11. Why use Federations?
Build Multi-tenant Solutions
– Single tenants per db works… But what about very small tenants
and very large tenants?
Tenant Management with Federations
– Federations makes tenant placement and replacement easy.
– Change your tenant placement any time without downtime.
Single tenant per database
Multiple-tenants per database Multiple databases per tenant
15. What is Data Explorer?
• Lightweight ETL tool to create data Mashups
• Designed to be used by subject matter experts
• Local or Cloud
Discover Enrich Publish
16. How do I get Data Explorer?
• Download and use the Desktop Client
• Use the cloud-based service
22. Microsoft Mobile Cloud BI V2.0 Updates
V2 Themes:
1. Move default server to new
Windows Azure server
2. Take advantage of WP7
Metro themes
The configuration settings area is
now available in the WP7 menu
selector ellipses at the bottom of
the screen:
• Reset Values: Reset app to
original config
• Set Server: Points to your own
SQL Azure Reporting Server
• Report 1-5: Set the RDL name
of your own reports
23. How to Customize App
• You can use this App to render your own SQL Azure
Reporting Services Reports
– Click menu bar: Select Set Server
– Enter your SQL Azure Reporting Services full server name,
without https://
– Go to menu bar: Select each Report # menu item
– Enter the name of your report file, without the .rdl extension
• Default login for demo out of the box
– Username = demo
– Password = Microsoft1
24. First time that your
start the App, you must
enter user name and
password.
This is from SQL Azure
Reporting Services.
Use demo/Microsoft1 read-
only report viewer
account.
25. Home reporting page
defaults to scorecard.
Select a single KPI from
the KPI tracker to appear
on your WP7 start page.
Select the KPI from WP7
menu ellipses.
27. Because reports and KPIs
are from SQL Azure and
SQL Azure Reporting
Services, users can
modify the content and
reports.
This is not a static
mock-up. This is
real, live data and
reporting.
28. Use SQL Azure and SQL
Azure Reporting Services
to create new data, new
reports and modify source
to demonstrate to
customers the dynamic
data.
No need to modify the
App.
30. Live Tile shows your chosen
top-line KPI value when you
add App to home screen
with “Pin to Start”
Select the email link from the
ellipses menu button to
email a copy of the current
report to your contacts
31. Azure Components of Cloud BI
Requires reports to be authored
in SQL Azure Reporting Services
Uses an Azure WCF Service to
update KPIs
Requires SQL Azure database
(AdventureWorksDW2008R2)
32. Offline Viewing
• KPIs and settings saved in WP7 Isolated
Storage
• View latest KPIs with offline browsing
Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later)Explain at a high level how SQL Azure worksSpeaker NotesDesign Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low frictionSQL Azure is a high availability databaseAlways three transaction consistent replicas of the databaseOne primary replica; two slave replicasFailure of a replica will result in another replica being spun up immediately by the fabricFailure of the primary replica means a slave replica will become the primary and a new slave will spin upMinimal down timeTypically just a few dropped connectionsEasy to code for the failover scenario- if you are ding god connection management and error handling will be fineClustered index required on all tables to allow replicationNotesUseful article from SQL Azure teamhttp://msdn.microsoft.com/en-us/magazine/ee321567.aspxSQL Azure Architecture OverviewAs discussed earlier, each SQL Azure database is associated with its own subscription. From the subscriber’s perspective, SQL Azure provides logical databases for application data storage. In reality, each subscriber’s data is actually stored multiple times, replicated across three SQL Server databases that are distributed across three physical servers in a single data center. Many subscribers may share the same physical database, but the data is presented to each subscriber through a logical database that abstracts the physical storage architecture and uses automatic load balancing and connection routing to access the data. The logical database that the subscriber creates and uses for database storage is referred to as a SQL Azure database
Elastic ScaleService scales as resources requirements growNo-Code Sync ConfigurationEasily define data to be synchronizedSchedule SyncChoose how often data is synchronizedConflict HandlingHandle issues where same data is changed in multiple locationsLogging and MonitoringAdministration capabilities for tracking data and monitoring potential issues
Main site link - http://www.microsoft.com/en-us/sqlazurelabs/labs/dataexplorer.aspxDesktop client download - http://www.microsoft.com/download/en/details.aspx?id=28349Request to sign up for the cloud-service - https://dataexplorer-signup.sqlazurelabs.com/