Intelligence Artificial Intelligence Ian Gent [email protected] Practical 2: Forward Checking.
Practical businerss intelligence in share point 2013
28
Ivan Sanders SharePoint MVP/MCT [email protected] @iasanders Practical Business Intelligence in SharePoint 2013
-
Upload
ivan-sanders -
Category
Documents
-
view
598 -
download
2
description
Transcript of Practical businerss intelligence in share point 2013
Ivan SandersSharePoint MVP/[email protected]@iasanders
Practical Business Intelligence in SharePoint 2013
• Introductions• Architecture• Installation Configuration• Design & Development• Packaging and Deployment• QA• Who do you trust
Outline & Agenda
Ivan SandersIvan Sanders is a SharePoint MVP/MCT Author and independent consultant with more than 15 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, SharePoint ShopTalk, INETA, GITCA, and Local Southern California User Groups.
twitter http://twitter.com/iasanders, LinkedIn http://www.linkedin.com/in/iasanders, Blog http://msmvps.com/blogs/ivansanders MVP Profile https://mvp.support.microsoft.com/profile/Ivan.Sanders .
Demo
Kick-Off the Installation and Configuration
Demo + Codehttp://bit.ly/kOqLnv
Requirements
Web & Application ServersSingle Server Farms• SharePoint 2010 vs. SharePoint “2013”
Comparison:Component
SharePoint 2010 Minimum Requirement
SharePoint “2013” Minimum Requirement
Processor 64-bit, four cores 64-bit, four cores
RAM 4 GB for developer or evaluation use8 GB for production use in a single server or multiple server farm
4 GB for developer or evaluation use8 GB for production use in a single server or in a multiple server farm
Hard disk 80 GB for system drive
Maintain twice as much free space as you have RAM for production environments.
80 GB for system drive
Maintain twice as much free space as you have RAM for production environments.
Database ServersMinimum Hardware Requirements• SharePoint 2010 vs. SharePoint “2013”
Comparison:Component
SharePoint 2010 Minimum Requirement
SharePoint “2013” Minimum Requirement
Processor 64-bit, 4 cores for small deployments64-bit, 8 cores for medium deployments
64-bit, 4 cores for small deployments64-bit, 8 cores for medium deployments
RAM 8 GB for small deployments16 GB for medium deployments
8 GB for small deployments16 GB for medium deployments
Hard disk 80 GB for system driveHard disk space is dependent on the size of your SharePoint content
80 GB for system driveHard disk space is dependent on the size of your SharePoint content
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 NA
SSD Disk Usage Strongly recommended NA
Network speed Important Important
Concurrency Pretty good Not enough experience…
• Plan for Tabular and PowerPivot memory usage
• Just because you can, Doesn’t mean you should
• Don’t even think about installing your DEV system with 4GB though you may be able to use 8GB the minimum you should have is 16GB
Best Practices
Architecture
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
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
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
Installation & Configuration
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
Design & Development
The Business Data Continuum
Operational Databases
Data Consolidation & Transformation
(ETL)
Relational Data Warehouse
OLAP CubesORTabular Data
Reports, Charts, Dashboards & Scorecards
Right-Sizing SolutionsBusiness Needs
Gather Analytical
Requirements
Design Dimensional
Model
Design Data Transformatio
ns
Create OLAP Dimensions &
Cubes
Design Reports & Analytics
Design Presentation
Portal
BI Solution Design Phases & Components
SQL File Data Flow
SQL Server Relational
Integration Services
AnalysisServices
ReportingServices
SharePointServices
What tool should I use? When?
PerformancePoint
SSAS
Grids Graphs
Exploration
Value Based
GaugesScorecards
Sparklines
Diagrams
SSRS
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.
• Everything should be packages as a WSP or it doesn’t get deployed.
• There should never be manual changes made by developers to UAT or PRD. Developers shou7ld not have access to the environment beyond their normal User Rights
Best Practices
QA
Who Do you trust??• Maurice Prather http://www.bluedoglimited.com/default.aspx • Andrew Connell http://www.andrewconnell.com/blog • Spence Harbar http://www.harbar.net • Heather Solomon http://www.heathersolomon.com/blog • Todd Klindt http://www.toddklindt.com/default.aspx• Todd Baginski http://www.toddbaginski.com/blog • Todd Bleeker http://bit.ly/edlSm5
Jan Tielens http://weblogs.asp.net/jan • Patrick Tisseghem http://www.u2u.info/Blogs/Patrick/default.aspx • Wictor Wilen http://www.wictorwilen.se • Ted Patisson http://blog.tedpattison.net/default.aspx • Lars Fastrup http://www.fastrup.net • Carsten Keutmann http://keutmann.blogspot.com• Keith Richie http://blog.krichie.com• Bill Baer http://blogs.technet.com/b/wbaer • Sahil Malik http://blah.winsmarts.com • Bil Simser http://weblogs.asp.net/bsimser • Ivan Sanders http://msmvps.com/blogs/ivansanders• Gary LaPointe http://blog.falchionconsulting.com• Shanon Bray http://shannonbray.wordpress.com
THANK YOU
Codeplex – with Source Code• http://cksdev.codeplex.com • http://startermasterpages.codeplex.com • http://spm.codeplex.com • http://autospinstaller.codeplex.com • http://spsf.codeplex.com • http://slk.codeplex.com • http://smarttools.codeplex.com • http://spviewpermission.codeplex.com• http://bidshelper.codeplex.com • http://almspecialisttoolkit.codeplex.com • http://spsf.codeplex.com
