3. Ivan Sanders
Ivan Sanders is a SharePoint MVP/MCT Author and independent consultant with more than
20 years of broad-based hands-on experience with the design and development of
mission-critical applications that include Business Intelligence Dashboards in the enterprise
and deployment of Microsoft products, while delivering nothing but Microsoft SharePoint
solutions since 2004.
Ivan is active in the SharePoint Community through the MSDN and TechNet forums, Teched
and PDC Birds of a Feather, SharePoint Saturday, SharePoint Conferences, Teched, Build,
SharePoint ShopTalk, INETA, GITCA, and Local Southern California User Groups.
FOLLOWME:
twitter http://twitter.com/iasanders
LinkedIn http://www.linkedin.com/in/iasanders,
Blog http://blogs.msmvps.com/ivansanders
MVP Profile http://mvp.microsoft.com/en-us/MVP/Ivan%20Sanders-4028951
Just the CODE and DEMOS
Download the demos http://sharepointdemobuilds.codeplex.com
More Code on GitHub: https://github.com/iasanders
By Norman P. Warren, Mariano
Teixeira Neto, Stacia Misner, Ivan
Sanders, Scott A. Helmers
May 2013, ISBN 978-0-7356-7543-8
406 pages, $34.99
6. Web & Application Servers
Single Server Farms
• SharePoint 2010 vs. SharePoint “2013” Comparison:
Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum Requirement
Processor 64-bit, four cores 64-bit, 16 cores
RAM 8 GB for developer or evaluation use
16 GB for production use multiple server
farm
32GB in a single server farm
16 GB for developer or evaluation use
32 GB per server for production use in a
multiple server farm
64GB in a single server farm
Hard disk 80 GB for system drive
Maintain twice as much free space as you
have RAM for production environments.
120 GB for system drive
Maintain twice as much free space as you
have RAM for production environments.
7. Database Servers
Minimum Hardware Requirements
• SharePoint 2010 vs. SharePoint “2013” Comparison:
Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum Requirement
Processor 64-bit, 4 cores for small deployments
64-bit, 8 cores for medium deployments
64-bit, 16 cores for small deployments
64-bit, 32 cores for medium deployments
RAM 8 GB for small deployments
16 GB for medium deployments
64 GB for small deployments
128 GB for medium deployments
Hard disk 80 GB for system drive
Hard disk space is dependent on the size
of your SharePoint content
120 GB for system drive
Hard disk space is dependent on the size of
your SharePoint content
8. OLAP vs. Tabular Considerations
Feature Multidimensional Tabular
RAM Some (16/32 GB) A lot (64/128)
RAM Speed Important Crucial
Number of cores 4/8/16 4/8/16
Core speed Less Important Crucial
Disk speed Very Important Very Important
SSD Disk Usage Strongly recommended NA
Network speed Important Important
Concurrency Pretty good Pretty Good
10. SharePoint 2013 Architecture
• In general the model has stayed same
as in previous version
• Numerous platform level
improvements and new capabilities
• Shredded Storage
• SQL Improvements
• Cache Service
• Request Management
• Themes
• Sharing
11. Business Intelligence
• Excel Client
• Instant analysis through In Memory BI
Engine
• Power View
• Power Pivot
• Excel Services
• Improved data exploration
• Field List and Field Well Support
• Calculated Measures and Members
• Enhanced Timeline Controls
12. Business Intelligence
• PerformancePoint Services
• Filter enhancements and Filter search
• Dashboard migration
• Support for Analysis Services Effective User
• Visio Services
• Refresh data from external sources – BCS
and Azure SQL
• Supports comments on Visio Drawings
• Maximum Cache Size service parameter
• Health Analyzer Rules to report on
Maximum Cache Size
13. Visio Services Architecture
Visio Web
Access
Custom Data
Providers
Visio JSOM
Mash-Up API
Web Part
Connections
Visio Proxy
Visio Graphics Service
VDW/b/m
SharePoint Content DatabaseExternal Data Sources
Web Front
End
Application
Server
Backend SQL OLEDB/ODBCXLSX SP Lists
SQL
Azure
External
Lists
14. Excel Services Architecture
Excel Web Access
Excel Web
Services
JSOMREST API
Excel Proxy
User-Defined Functions Excel Calculation Service
XLSX/b/m
SharePoint Content DatabaseExternal Data
Sources
Web Front
End
Application
Server
Backend
15. Excel Business Intelligence Architecture
Tabular
Multi-
dimensional
Data Model
External Data
Sources
Presentation
BI Semantic
Model
ROLAP
Excel 2013
SharePoint Insights
Power View
Business logic and queries
Data access
MDX DAX
MOLAP xVelocity
Direct
Query
OData FeedsDatabases Hadoop
SQL Azure
&
Cloud
…and more
16. PerformancePoint Services Architecture
Web Parts
Web Services
Rendering
Custom Editors
Web Services
Authoring
SharePoint Data Store
Monitoring Services
Application Proxy
Data Source Extensibility
PPS App Settings
SharePoint Repository
PerformancePoint
Services WCF Interface
External Data
Sources
Client
Web
Front
End
Application
Server
Backend
HTTP/HTML AJAX/JSON SOAP/XML
SharePoint Data Store
18. Best Practices
1. If you haven't created a SQL Installation Answer file or a
PowerShell script there is no time like the present
2. Download AutoSpInstaller
http://autospinstaller.codeplex.com
• Modify the AutoSPInstallerInput.xml with your company SharePoint Service Accounts,WebApps etc.
Like SPService, SPAdmin, SPSearch, SPFarm, SPCrawl, SPMySite, SPWebApp. SQLService, SQLAdmin
• Modify the search index location
• Set WebAnalyticsService Provision="false“
• Extract the Binaries to disk
• There is a new GUI for helping you to enter your information if you don’t have an xml editor
• One of the many cool things is if the script fails, just modify the input file and run again it will start where it left off
3. Complete post-deployment tasks as required
20. The Business Data Continuum
Operational Databases
Data Consolidation
& Transformation
(ETL)
Relational Data
Warehouse
OLAP Cubes
OR
Tabular Data
Reports, Charts,
Dashboards & Scorecards
22. Gather Analytical
Requirements
Design Dimensional
Model
Design Data
Transformations
Create OLAP
Dimensions &
Cubes
Design Reports &
Analytics
Design Presentation
Portal
BI Solution Design Phases & Components
SQL File
Data
Flow
SQL Server
Relational
Integration
Services
Analysis
Services
Reporting
Services
SharePoint
Services
23. What tool should I use? When?
PerformancePoint
SSAS
Grids Graphs
Exploration
Value Based
GaugesScorecards
Sparklines
Diagrams
SSRS
24. Why Tabular?(xVelocity/Vertipaq engine)
• The current process for analytics idea to implementation is way too long.
• Everyone is familiar with Excel.
• Tabular is easier and faster than OLAP !!!
• Query tool (DAX) is easier than MDX
• Most important: You will quickly make your users heroes when
introducing self-service analytics and reporting in Power View.
25. Codeplex
All Business Intelligence Demo installation packages
http://sharepointdemobuilds.codeplex.com
SUSHI 5.x for SharePoint 2013
http://sushi.codeplex.com/releases/view/612322
26. SharePoint 2013 Business Intelligence Demo
Builds with SQL Server 2012 or SQL 2014
The following Demos are available for download and should be
installed in the order presented below
1.Active Directory Content Pack Demo 2.0
2.SQL 2012 SP1 Content Pack Demo 2.0
3.SharePoint 2013 Configuration Demo 2.0
4.PeoplePack - UserProfile Provisioning Demo 2.0
5.Self-Service BI Demo 2.0 Content Pack
6.Visio Services Demo 2.0 Content Pack
Ideas are brought to the team or we think of them (ex: How customers engage with our products?)
Identify the data, clean it, and capture it.
Build a report in the DW.
This usually takes 4, 5, or 6 weeks depending on the data, report, etc.
Often times when the stakeholder looks at the report, they say something like "Now that I see this, I really want X.“