1. SQL Server 2016 Business Intelligence Upgrade Planning
SQL Server 2016 is one of the largest SQL Server releases ever. In the latest offering, Microsoft has delivered many exciting new features across the relational database engine, integration and business intelligence solutions. Since SQL Server implementations and used features vary widely, no upgrade is the same. In this session, we will walk through the steps to assess your SQL Server environment and plan for a successful upgrade. Session topics include:Upgrade Planning Assessment
Unsupported Scenarios
Pre-upgrade Tasks and Tools
Upgrade Methods
Post-upgrade Tasks

2. About the Speaker Jen Underwood Founder & Principal Consultant
~20 years of industry experience
Former Microsoft BI Principal Program Manager and Big-Four BI Practice Lead
Passionate technology blogger and industry analyst
Bachelor Business Administration – Univ. of Wisconsin Milwaukee Post Graduate Computer Science – Data Mining Univ. of California, San Diego

3. Agenda Preparation and Tools Developing Upgrade Plans
Upgrade Approaches
Database, Business Intelligence and other Components
Additional Resources

4. Must Read / Do Get support for adequate upgrade planning time
Run Best Practices Analyzer
Run Upgrade Advisor
Review deprecated features
Review Known Issues Read Upgrade Technical Guide
Review SQL Server upgrade docs
Source: Introducing-SQL-Server-2016-eBook-2.html
Best practices
Upgrade Advisor
eBook

5. CHOOSE AN EDITION

6. Best Practices Analyzer
Run on legacy instances of SQL Server
Address any issues before upgrade
Eases upgrades to newer versions
You should run the SQL Server Best Practices Analyzer (BPA) against your legacy instances of SQL Server. If bad or questionable practices exist, you could address them before the upgrade, moving the fixes through test and into production. Using best practices on the legacy SQL Server systems first will help ensure a smoother upgrade, but that is not always possible. You might have to change some practices during the upgrade process instead

7. Upgrade Advisor DBA Workbench
Download:

8. As with previous releases, there is once again an Upgrade Advisor for SQL Server However, this version is completely different from its predecessors, and is available in preview from today - long before the release of SQL Server 2016! In addition, there is a new feature available here, called the Stretch Database Advisor, which will help provide guidance about tables that might be good candidates for this new SQL Server 2016 feature.
it shows a breakdown for all compatibility levels above the database's current level.
The tool should provide at least warnings for all of the items in the official documentation. If more coverage isn't supplied in future versions, you will still be left to your own devices to assess the risk and effort that will be involved in an upgrade

9. Demo
#ITDevConnections

10. Allowable Upgrade Paths
SQL Server 2016 supports upgrades
SQL Server 2008 SP3 or later
SQL Server 2008 R2 SP2 or later
SQL Server 2012 SP1 or later
SQL Server 2014 or later
Upgrade from SQL Server 2005 requires migration via back up/ restore or attach, see docs online
Source:
SQL Server 2016, you will be able to do the following:
Attach a SQL Server 2005 database (mdf/ldf files) to SQL Server 2016 instance of database engine.
Restore a SQL Server 2005 database to SQL Server 2016 instance of database engine from a backup.
Back up a SQL Server 2005 Analysis Services (SSAS) cube and restoring on SQL Server 2016.

11. Unsupported Scenarios
Windows Server or Windows 8+ on x64 processors only
Minimum 6 GB space even if components installed elsewhere
No installs on read-only, mapped, or compressed drives
No in-place upgrade to different 32/64 bit version
No in-place upgrade from SQL Server 2005 or lower version
No cross-version instances of SQL Server 2016
Failover Clusters are not supported in WOW mode
Upgrade from an Evaluation edition of a previous SQL Server version
Source:
Source:
Exceptions to the operating system support noted in this section are the following Business Intelligence features, which can be installed on Windows Server 2008 R2 SP1 or later:
Reporting Services – SharePoint and Reporting Services Add-in for SharePoint products

12. Source: https://msdn.microsoft.com/en-us/library/mt551979.aspx

13. Source: https://msdn.microsoft.com/en-us/library/mt551979.aspx

14. Developing Upgrade Plans

15. Developing an Upgrade Plan
Treat upgrades as an IT Project
Minimize variables during upgrades
Evaluate potential issues early
Review apps and connections ecosystem
Define success criteria and rollback
Create upgrade checklists

16. Environment Assessment
Inventory servers, services, and configurations
CPU, Memory, OS, drive space, and note if clustered
SQL Server components used and note if clustered
High availability, replication, log shipping and back ups
Maintenance plans and jobs
Databases, encryptrion keys, user and service accounts
Developers, applications and connection changes
3rd party controls, utilities, .dlls, and downstream services
Upgrade Advisor warnings

17. Example

18. Example

19. Demo
#ITDevConnections

20. Upgrade APPROACHES

21. Upgrade Options Upgrade in-place Side-by-side installation
Perform a rolling upgrade
A rolling upgrade is required in SQL Server solution environments involving multiple SQL Server instances that must be upgraded in a certain order to maximize uptime, minimize risk, and preserve functionality.

22. Upgrade In-Place Easiest upgrade type
Plan for downtime, challenging to rollback
SQL Server setup upgrades existing install bits, then system and user databases
Source:
With this approach, the SQL Server setup program upgrades the existing SQL Server installation by replacing the existing SQL Server bits with the SQL Server 2016 bits and then upgrades each of the system and user databases. The upgrade in-place approach is easiest, requires some amount of downtime, takes longer to fallback if a fallback is necessary, and it is not supported for all scenarios. For more information on supported and unsupported upgrade in-place scenarios, see Supported Version and Edition Upgrades.
This approach is frequently used in the following scenarios:
A development environment without a high-availability (HA) configuration.
A non-mission critical production environment that can tolerate downtime and that is running on a recent hardware and software.
The amount of downtime is dependent upon the size of your database and the speed of your I/O subsystem.
Upgrading SQL Server when memory-optimized tables are in use will take some extra time. For more information, see Plan and Test the Database Engine Upgrade Plan.

23. In-Place Considerations
Advantages
Easier and faster
Applications connect to same instance name
No additional hardware Additional disk space
Mostly automated
Disadvantages
Upgrade whole instance or a major component
Need to address blockers
Unable to compare since replaces existing install
Rollback more complicated
The overall advantages of an in-place upgrade include the following:
 An in-place upgrade can be easier and faster, especially for small systems, because data and configuration options do not have to be manually transferred to a new server.
 It is mostly an automated process.
 The resulting upgraded instance has the same name as the original.
 Applications continue to connect to the same instance name.
 No additional hardware is required because only the one instance is involved. However, additional disk is required by the Setup program.
 Because it is mostly automated, it takes the least amount of deployment team resources.
Some overall disadvantages of an in-place upgrade include the following:
 You must upgrade the whole instance or a major SQL Server component. For example, you cannot directly upgrade a single database.
 You must inspect the whole instance for backward-compatibility issues and address any blocking issues before SQL Server Setup can continue.
 Upgrading in place is not recommended for all SQL Server components, such as some DTS packages.
 Because the new instance of SQL Server 2016 replaces the legacy instance, you cannot run the two instances side by side to compare them. Instead, you should use a test environment for comparisons.
 Rollback of upgraded data and the upgraded instance in an in-place upgrade can be complex and time-consuming.

24. Side-by-Side More time consuming, safer approach to rollback
Build new SQL Server 2016 environment
Manually migrate settings, user databases, jobs, SSIS, SSAS and SSRS content
Backup/restore
In a side-by-side upgrade, instead of directly replacing the older instance of SQL Server, required database and component data is transferred from a legacy instance of SQL Server 2005/2008/2008 R2/2012 to a separate instance of SQL Server It is called a "side-by-side" method because the new instance of SQL Server 2016 runs alongside the legacy instance of SQL Server, either on the same server or on a different server.
There are two important options when you use the side-by-side upgrade method:
 You can transfer data and components to an instance of SQL Server 2016 that is located on a different physical server or on a different virtual machine.
 You can transfer data and components to an instance of SQL Server 2016 on the same physical server.
key point in a side-by-side upgrade is that you must manually transfer data files and other supporting objects from the older instance of SQL Server to the instance of SQL Server The SQL Server Setup program will not perform this task. The objects that you must transfer include the following:
 Data files and Database objects
 SQL Server Analysis Services (SSAS) cubes
 Configuration settings
 Security settings
 SQL Server Agent jobs
 SQL Server Integration Services (SSIS) packages

25. Migrate to a new installation
Source:
Migrate to a new installation
With this approach, you maintain the current environment while you build a new SQL Server 2016 environment, frequently on new hardware and with a new version of the operating system. After installing SQL Server 2016 in the new environment, you perform a number of steps to prepare the new environment so that you can migrate the existing user databases from the existing environment to the new environment and minimize downtime. These steps include migrating the following:
System objects: Some applications depend on information, entities, and/or objects that are outside of the scope of a single user database. Typically, an application has dependencies on the master and msdb databases, and also on the user database. Anything stored outside of a user database that is required for the correct functioning of that database must be made available on the destination server instance. For example, the logins for an application are stored as metadata in the master database, and they must be re-created on the destination server. If an application or database maintenance plan depends on SQL Server Agent jobs, whose metadata is stored in the msdb database, you must re-create those jobs on the destination server instance. Similarly, the metadata for a server-level trigger is stored in master. When you move the database for an application to another server instance, you must re-create all the metadata of the dependant entities and objects in master and msdb on the destination server instance. For example, if a database application uses server-level triggers, just attaching or restoring the database on the new system is not enough. The database will not work as expected unless you manually re-create the metadata for those triggers in the master database. For detailed information, see Manage Metadata When Making a Database Available on Another Server Instance (SQL Server)
Integration Services packages stored in MSDB: If you are storing packages in MSDB, you will need to either script out those packages using the dtutil Utility or redeploy them to the new server. Before using the packages on the new server, you will need to upgrade the packages to SQL Server For more information, see Upgrade Integration Services Packages.
Reporting Services encryption keys: An important part of report server configuration is creating a backup copy of the symmetric key used for encrypting sensitive information. A backup copy of the key is required for many routine operations, and enables you to reuse an existing report server database in a new installation. For more information, see Back Up and Restore Reporting Services Encryption Keys and Upgrade and Migrate Reporting Services
Once the new SQL Server 2016 environment has the same system objects as the existing environment, you then migrate the user databases from the existing system to the SQL Server 2016 instance in a manner that will minimize downtime on the existing system. You accomplish the database migration either using backup and restore, or by repointing LUNs if you are in a SAN environment. The steps for both methods are delineated in the diagrams below.

26. Side-by-Side Considerations
Advantages
Much more control on granular level upgrades
Old server can keep running
Easier to rollback
Disadvantages
More complicated and slower process
Manual transfer tasks
Might require new hardware
Change apps connections
Potential data sync needed
The overall advantages of a side-by-side upgrade include the following:
 It gives more granular control over which database objects are upgraded.
 The legacy database server can run alongside the new server. You can perform test upgrades and research and resolve compatibility issues without disturbing the production system.
 The legacy database server remains available during the upgrade, although it cannot be updated for at least the time that is required to transfer data.
 Users can be moved from the legacy system in a staged manner instead of all at the same time. Even though your system might have passed all validation and acceptance tests, a problem could still occur. But if a problem does occur, you will be able to roll back to the legacy system.
The overall disadvantages of a side-by-side upgrade include the following:
 A side-by-side upgrade might require new or additional hardware resources.
 If the side-by-side upgrade occurs on the same server, there might be insufficient resources to run both instances alongside one another.
 Applications and users must be redirected to a new instance. This redirection might require some recoding in the application.
 You must manually transfer data—as well as security, configuration settings, and other supporting objects
 Synchronization of data from the legacy server to a new server will be required to capture data modifications that occurred to the legacy system while setting up the new system and its original copy of the data.

27. Rolling Upgrade Multiple instances that need “ordered” upgrades
More complex for planning
Always-On Availability Groups: Upgrading Always On Availability Groups
Failover clustering instances:  Upgrade a SQL Server Failover Cluster Instance
Mirrored instances:  Upgrading Mirrored Instances
Log shipping instances:  Upgrading Log Shipping to SQL Server 2016
Replication environment: Upgrade Replicated Databases
Reporting Services scale-out environment: Upgrade Reporting Services
Rolling upgrade
A rolling upgrade is required in SQL Server solution environments involving multiple SQL Server instances that must be upgraded in a certain order to maximize uptime, minimize risk, and preserve functionality.
These are documented in the following topics:
Always-On Availability Groups: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Always On Availability Group Replica Instances.
Failover clustering instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrade a SQL Server Failover Cluster Instance
Mirrored instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Mirrored Instances.
Log shipping instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Log Shipping to SQL Server 2016 (Transact-SQL)
A replication environment: For detailed steps for performing a rolling upgrade in this environment, see Upgrade Replicated Databases
A SQL Server Reporting Services scale-out environment: For detailed steps for performing a rolling upgrade in this environment, see Upgrade and Migrate Reporting Services.

28. Database, Business Intelligence and other Components

29. Components Database Engine SQL Server Management and Development Tools
Data Quality Services
Master Data Services
Integration Services
Analysis Services
Reporting Services
SharePoint BI

30. Database Engine
Choose in-place, side-by-side or rolling upgrade approach
After upgrade, additional steps include taking a new backup, enabling new features, and re-populating full-text catalogs
Change Database Compatibility Mode and Use Query Store 
The topics in this section will help you upgrade the SQL Server database engine from a prior release of SQL Server to SQL Server 2016.
Choose a Database Engine Upgrade Method Before beginning an upgrade, you need to understand the various upgrade methods. This topic discusses the upgrade methods and the steps involved with each upgrade method.
Plan and Test the Database Engine Upgrade Plan After reviewing the upgrade methods, you are ready to develop the appropriate upgrade method for your environment and then test the upgrade method before upgrading the existing environment. This topic discusses developing an upgrade plan and testing it.
Complete the Database Engine Upgrade After your databases have been upgraded to SQL Server 2016, there are additional steps you need to take, including taking a new backup, enabling new features, and re-populating full-text catalogs. This topic discusses these steps.
Change the Database Compatibility Mode and Use the Query Store One of the steps to take after your databases have been upgraded to SQL Server 2016 is to enable new features by changing the database compatibility mode and then using the query store to monitor performance. This topic discusses this process and provides a recommended workflow.
Source:

31. Query Stability Upgrade to SQL 2016 Keep 110/120 CompatLevel
Freeze plans (optional)
Run Query Store (establish perf. baseline)
Move to 130 CompatLevel and unfreeze plans
Monitor perf. and fix regressions with plan forcing
Source:
Query store is a new feature in that provides DBAs with insight on query plan choice and performance. It simplifies performance troubleshooting by enabling you to quickly find performance differences caused by changes in query plans. The feature automatically captures a history of queries, plans, and runtime statistics, and retains these for your review. It separates data by time windows, allowing you to see database usage patterns and understand when query plan changes happened on the server. The query store presents information by using a Management Studio dialog box, and lets you force the query to one of the selected query plans. For more information, see Monitoring Performance By Using the Query Store.
Enabling the Query Store
Query Store is not active for new databases by default.
Maintaining Query Performance Stability
For queries that are executed multiple times you may notice that SQL Server used different plans which resulted in different resource utilization and duration. With Query Store you can easily detect when the query performance regressed and determine the optimal plan within a period of interest. Then you can force that optimal plan for future query execution.
You can also identify inconsistent query performance for a query with parameters (either auto- parameterized or manually parameterized). Among different plans you can identify plan which is fast and optimal enough for all or most of the parameter values and force that plan; keeping predictable performance for the wider set of user scenarios.
Force or a plan for a query (apply forcing policy). When a plan is forced for a certain query, every time a query comes to execution it will be executed with the plan that is forced.
EXEC = = 49;
When using sp_query_store_force_plan you can only force plans that were recorded by Query Store as a plan for that query. In other words, the only plans available for a query are those that were already used to execute Q1 while Query Store was active.
Remove plan forcing for a query. To rely again on the SQL Server query optimizer to calculate the optimal query plan, use sp_query_store_unforce_plan to unforce the plan that was selected for the query.
EXEC = = 49;
Other notes:
De-risk upgrades: QDS PF and COMPAT LEVEL
All plans are freezed in pre-upgrade state
We changed QP to keep CE changes under compat level
Questions:
Would described scenario work in your environment?
plan freezing will keep your current forcing decisions and apply the LAST plan for other queries. Is that what you would expect?

32. Replicated Databases
SQL Server 2016 supports upgrading replicated databases from previous versions of SQL Server
Do not need to stop activity at other nodes while a node is being upgraded
Distributor can be any version >= Publisher version
Publisher can be any version <= Distributor version
Subscriber version depends on type of publication
Source:
SQL Server 2016 supports upgrading replicated databases from previous versions of SQL Server; it is not required to stop activity at other nodes while a node is being upgraded. Ensure that you adhere to the rules regarding which versions are supported in a topology:
A Distributor can be any version as long as it is greater than or equal to the Publisher version (in many cases the Distributor is the same instance as the Publisher).
A Publisher can be any version as long as it less than or equal to the Distributor version.
Subscriber version depends on the type of publication:
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2012 Publisher can have SQL Server 2014 and SQL Server 2016 Subscribers; and a SQL Server 2016 Publisher can have SQL Server 2014 and SQL Server 2012 Subscribers.
A Subscriber to a merge publication can be any version less than or equal to the Publisher version.

33. Data Quality Services
Back up DQS databases before upgrading to prevent data loss from schema upgrade
Need to use matching versions Add-Ins for Excel
Source:
You must back up your DQS databases before upgrading DQS to prevent any accidental data loss during the schema upgrade. For information about backing up DQS databases, see Backing Up and Restoring DQS Databases.
You can connect to the SQL Server 2016 version of Data Quality Server by using the current or an earlier version of Data Quality Client or the DQS Cleansing Transformation in Integration Services to perform your data quality tasks.
After upgrading Data Quality Services and Master Data Services to SQL Server 2016, any earlier version of the Master Data Services Add-In for Excel will no longer work. You can download the SQL Server 2016 version of Master Data Services Add-In for Excel from here.

34. Master Data Services MDS
Back up MDS databases before upgrading
Warning customizations to may be overwritten
Need to use 2016 Web App, extra steps to reuse IIS alias
Need to use matching versions Add-Ins for Excel
Source:
Back up your database before performing any upgrade.
The upgrade process recreates stored procedures and upgrades tables used by Master Data Services. Any customizations you have made to either of these components may be lost.
Model deployment packages can be used only in the edition of SQL Server they were created in. You cannot deploy model deployment packages created in SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 to SQL Server 2016.
After upgrading Data Quality Services and Master Data Services to SQL Server 2016, any earlier version of the Master Data Services Add-In for Excel will no longer work. You can download the SQL Server 2016 Master Data Services Add-In for Excel from Microsoft Download Center .
Your existing MDS web application from an earlier version of SQL Server (SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014) is available for selection in the SQL Server 2016 version of Master Data Services Configuration Manager. You must not select the existing web application, and instead must create a SQL Server 2016 web application for MDS. Otherwise, you will receive an error when you try to associate the web application with the upgraded MDS database stating that the requested page cannot be accessed because the related configuration data for the page is invalid.
If you want to use the same name (alias) for MDS web application as your existing (SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014) web application, you must first delete the web application and the associated application pool from IIS, and then create a web application with the same name using SQL Server 2016 version of Master Data Services Configuration Manager. For information about removing web application and application pools from IIS, see Remove an Application (IIS) and Remove an Application Pool (IIS).

35. Integration Services (SSIS)
Run Upgrade Advisor to catch discontinued features like DTS
Upgrade does not migrate existing packages – need to migrate packages afterward service upgrade completes
Upgrade packages with SSIS Package Upgrade Wizard
Developers can upgrade 2012/2014 projects to 2016 without manual adjustments after upgrade
Admins need to run DCOM Configuration to users access  
Source: ,
Support for migrating or running Data Transformation Services (DTS) packages has been discontinued in in the current release of SQL ServerIntegration Services. The following DTS functionality has been discontinued.
When you upgrade to SQL Server 2016 Integration Services (SSIS) on a machine that has one of these earlier versions of Integration Services installed, SQL Server 2016 Integration Services (SSIS) is installed side-by-side with the earlier version.
With this side-by-side install, multiple versions of dtexec utility are installed. To ensure that you run the correct version of the utility, at the command prompt run the utility by entering the full path (<drive>:\Program Files\Microsoft SQL Server\<version>\DTS\Binn). For more information about dtexec, see dtexec Utility.
Developer can deploy selected SSIS packages incrementally without deploying the whole project, therefore saving the deployment time
Project Upgrade Pain Point: During the project upgrade, UX layout or shared connection manager may not be upgraded successfully

36. Analysis Services (SSAS)
Run Upgrade Advisor to catch discontinued features
Review SQL Server 2016 Release Notes known issues
Backup all SSAS databases then attach or restore
To upgrade Tabular model, use 2016 SQL Server Data Tools (SSDT) to change the Compatibility Level – do not use SSMS
Identify a subset of reports and queries to confirm performance
Run DBCC to check database integrity
Source
Before upgrading to SQL Server 2016 Analysis Services, review the following:
SQL Server 2016 Release Notes describes known problems and workarounds.
Analysis Services Backward Compatibility summarizes discontinued, deprecated, and changed features. You should review these lists periodically to assess the impact of product changes to your models, scripts, or custom code. Typically, feature transitions are announced during pre-release of the next major release.
Tabular models and databases benefit the most from SQL Server This release offers a revised DirectQuery mode for Tabular models at compatibility level 1200, simplified by the removal of hybrid mode, the addition of query statements for retrieving a subset of data at design-time, and row-level security via DAX instead of row permissions in the backend database.
A second reason to upgrade is the new tabular metadata construction inside the model. A Tabular model at the new compatibility level 1200, whether created at or upgraded to that level, uses native terminology for object definitions, such as model, table, relationships, and columns, to describe its major elements.
To upgrade a Tabular model, use a version of SQL Server Data Tools (SSDT) built for this release to change the Compatibility Level property to SQL Server 2016 RTM (1200).
Do not use SSMS, code, or script to change the CompatibilityLevel. By itself, changing the property does nothing. Metadata conversion occurs in SSDT in response to the property update, followed by reopening project.

37. Reporting Services (SSRS)
Read about upgrading reports
Use System Configuration Checker (SCC) to scan the report server
Back up your encryption keys, report server databases, configuration files and any customizations to IIS
Use SSRS Configuration Manager to add servers to a scale-out upgrade
Source:
There are two general approaches to upgrading a Reporting Services deployment:
Upgrade: You upgrade the Reporting Services components on the servers and instances where they are currently installed. This is commonly called an “in place” upgrade. In-place upgrade is not supported from one mode of Reporting Services server to another. For example, you cannot upgrade a Native Mode report server to a SharePoint mode report server. You can migrate your report items from one mode to another. For more information, see the ‘Native to SharePoint Migration’ section later in this document.
Migrate: You install and configure a new SharePoint environment, copy your report items and resources to the new environment, and configure the new environment to use existing content. A lower level form of migration is to copy the Reporting Services databases, configuration files, and if you are using SharePoint mode, the SharePoint content databases.
SQL Server 2016 Reporting Services (SSRS) Native mode can be installed side-by-side with a SQL Server 2012 or SQL Server 2014 Native mode deployment.
There is no support for side-by-side deployments of SQL Server 2016 Reporting Services (SSRS) SharePoint mode and any previous versions of Reporting Services SharePoint mode components.
Upgrade Reports
Report definition (.rdl) files are automatically upgraded in the following ways:
When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 report server in the project properties, the report definition is saved in a schema that is compatible with the target server.
When you upgrade a Reporting Services installation to a SQL Server 2016 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site.
Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying problems in the report are detected. For more information, see Reporting Services Backward Compatibility.

38. SharePoint 2016 + SQL Server BI
4/17/2018
SharePoint SQL Server BI
Source:
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

39. SharePoint 2016 BI Key Points
4/17/2018
SharePoint 2016 BI Key Points
Excel Services are now part of Excel Online 2016
Office Online Server is a mandatory server
Configure Excel Online via PowerShell
New architecture enables substantial benefits .
Excel Services are now part of Excel Online 2016
Excel Services application is no longer hosted on SharePoint Server. Instead, use Excel Online
on Office Online Server 2016 (OOS), formerly known as Office Web Application Server (WAC)
Office Online Server is a mandatory server
Excel workbooks won’t open in the browser without it. Excel Web Parts won’t work without it.
Power Pivot, Visio Services and Reporting Services will have limited functionality without it.
Configure Excel Online via PowerShell
Excel Services features that require configuration can be configured using
PowerShell Cmdlets on Office Online Server 2016
New architecture enables multiple, substantial benefits
All Excel web functionality under one roof. Improved scalability of service.
Stay up-to-date with new features, improvements and bug fixes
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

40. (in PP4SP mode, for model processing)
4/17/2018
Server 2016
Services
Reporting Services (SSRS)
Power Pivot for SP
Recommended upgrade sequence
2016 desktop client
This combination won’t be supported because WAC13 does not integrate with either SSAS or the SharePoint BI add-ons.
Customers are advised to upgrade their WAC servers prior to their SharePoint servers.
To enable SharePoint BI features, SQL add-ons must be 2016 version
This combination will support basic Excel Online functionality including Data Model and external data access (refresh, OLAP, Tabular).
It won’t support SharePoint BI features because they don’t integrate with OOS16.
Workbooks created in previous versions of Excel desktop client can be utilized via MS BI Stack 2016.
This combination is not recommended. It has limited support for Excel 2016 workbooks and other limitations*.
Customers are advised to upgrade their AS servers prior to other servers in the stack.
View/Edit workbook with or w/o data model
Online Server (OOS) 2016
OLAP/Tabular interactivity
Refresh workbook
Use data model;
Use Power View
SSAS Server 2016
(in PP4SP mode, for model processing)
Refresh data model
MS SQL DB
SSAS
Tabular DB
SSAS
OLAP DB
Other
Data Sources
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

41. Critical Upgrade Notes
4/17/2018
Critical Upgrade Notes
Deploy Complete SharePoint SQL 2016 BI Stack
Access external data without upgrading SharePoint Server
Upgrade the stack bottom-up
Recommended upgrade BI Stack sequence is
1) SSAS 2016
2) Office Online Server
3) SharePoint 2016
4) SQL Server add-ons for SP 2016
2016 is backward-compatible with Excel clients
Deploy Complete SharePoint SQL 2016 BI Stack
In order to leverage SharePoint BI features provided by SQL add-ons,
the on-premises SQL Server BI 2016 has to be deployed in its entirety.
Access external data without upgrading SharePoint Server
To access external data (including the use of data model, connectivity to OLAP/Tabular),
neither the SharePoint Server nor the SQL add-ons need to be upgraded.
Upgrade the stack bottom-up
Recommended upgrade sequence of the MS BI Stack is:
AS 2016  OOS 2016  SharePoint 2016  SQL add-ons for SP 2016
2016 is backward-compatible with earlier Excel clients
Workbooks created in previous versions of Excel desktop can be utilized
Forward compatibility has limitations. Upgrade SQL BI Stack first and then Excel desktop.
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

42. Additional Resources
Upgrade Advisor -
Product Team Upgrade Video -
SQL Server -
Analysis Services -
Reporting Services -
Deprecated Features -
SQL Server 2014 Upgrade Technical Guide (Note: 2016 not yet published)
Community Blogs -
Upgrade Advisor -
Product Team Upgrade Video -
SQL Server -
Analysis Services -
Reporting Services -
Deprecated Features -
SQL Server 2014 Upgrade Technical Guide (Note: 2016 not yet published)
Community Blogs -

43. WIN Rate This Session Now! Tell Us What You Thought of This Session
Rate with Mobile App:
Be Entered to
WIN
Prizes!
Tell Us What You Thought of This Session
Select the session from the Agenda or Speakers menus
Select the Actions tab
Click Rate Session
Rate with Website:
Register at
Go to
Select this session from the list and rate it
#ITDevConnections