Spark the future.

May 4 – 8, 2015Chicago, IL

Upgrading to Microsoft SQL Server 2014 and to Microsoft AzureMike SheltonRoss Loforte

BRK2577

Preparing to Upgrade

Preparing to Upgrade

Research current environment • - MAP tool

Define a current environment baseline • - Run Performance Monitor • - Management Data Warehouse

Choose target environmentChoose an edition of SQL Server 2014 • - Allowed paths by Editions

Migration to Azure

DemoMicrosoft Assessment and Planning Toolkit

Mike Shelton

Choose Upgrade ToolsSQL Server 2014 Upgrade Advisor• Analyzes SQL no longer valid on SQL Server 2014• Generates a report

Requirements • Windows Vista SP1, Windows 7, or Window Server 2008

R2/2012/2012 R2 • The Microsoft .NET Framework 4 (the same version of

the .NET Framework included with SQL Server 2014 and Visual Studio 2010)

• Windows Installer 4.5 • Processor speed of at least 500 MHz • 15 MB of available hard disk space • Supports SQL Server SQL Server 2005, 2008, 2008 R2,

and 2012 • Download version is available as part of the

Microsoft SQL Server 2014 Feature Pack

DemoSQL Server 2014 Upgrade Advisor

Mike Shelton

Other Upgrade Tools Best Practices Analyzer for SQL Server 2005/2008

R2/2012• Gathers information about Microsoft SQL Server• Determines if the configurations are set according to the recommended best practices• Reports on all configurations, indicating settings that differ from recommendations• Indicates potential problems and Recommends solutions

download from: www.microsoft.com/download

SQL Server Profiler• Create and manage SQL traces • Replay SQL trace • Saved in a trace file or table, can later be analyzed

System Monitor• SQL Server: Deprecated Features Object

SQL Server 2014 Setup• System Configuration Checker For installation rules

DemoBest Practices Analyzer for SQL Server

Mike Shelton

Developing an Upgrade Plan

Upgrade Strategies In-Place upgradeRestrictions:• All SQL Server components be upgraded together • From a 32-bit instance to a 64-bit instance not supported • Complex restore policy

SQL Setup steps to upgrade:1. Installs prerequisites2. Checks for upgrade blocking issues 3. If pending restart exists, restart 4. Installs SQL Server 2014 executables and support files5. Stops the legacy SQL Server service, no longer available 6. Updates the selected component data and objects 7. Removes the legacy executables and support files

• SQL Server 2005/2008/2008 R2/2012 client tools not removed • Database compatibility level not changed

SQL Server 2005/8/R2Instance

SQL Server 2014 Instance

Setup Requirements for an In-Place Upgrade

SQL Server 2005: SP4 is required SQL Server 2008: SP2 is required SQL Server 2008 R2: SP1 is required SQL Server 2012: SP1 is required

• Sufficient disk space must be available for SQL Server 2014• Not supported: 32-bit to 64-bit (x86 to x64) versions and vice versa • Supported version of the Windows operating system

Upgrade Strategies Side-by-Side upgrade

• Manual intervention• Data files • Database objects • Configuration settings • Security settings • SQL Server Agent jobs • SQL Server Integration Services

(SSIS) packages • Need server and storage capacity• Application name changes• Simpler backup strategy

Compareand

Verify

SQL Server 2005/8/R2/2012Instance

SQL Server 2014Instance

Verified!

Moving the database• Backup/Restore Upgrade Method• Detach/Attach Upgrade Method• Copy Database Wizard Upgrade Method• Log Shipping

Pros• Easier, mostly automated• Generally fast overall process• System data upgraded• May require no additional hardware• Applications remain pointing to same

server/database name

Cons• Less granular control over upgrade

process – all or nothing• Instance remains offline during part of

upgrade• Not best practice for all components • Complex rollback strategy

Upgrade options and considerationsIn-Place

Pros• More granular control over upgrade process• Database level• Can be used to perform test migration• Document process & gather metrics• Ability to run systems side-by-side for parallel

runs• May require 3rd party application to keep both

in-sync• Relatively straightforward rollback strategy• Can leverage failover/switchover to reduce

downtime• Upgrade over time

Cons• Usually require additional hardware• Additional resources required if on same

server• Server/database name changes• Not practical for VLDB unless utilizing SAN

(hybrid approach)• Beware of “loss of quick roll-back”

Upgrade options and considerationsSide-by-side (migrate)

Software Requirements for SQL Server 2014

Setup will install .NET 4.0, the SQL Server Native Client, and support files

.NET requirements: • SQL Server 2014 on a Windows Server 2008 SP2 server, install .NET Framework 3.5 • On Windows 7 and Windows Server 2008 R2 SP1, enable .NET Framework 3.5

Windows PowerShell 2.0 is required

Application and Connection Requirements• SQL Server native Client 11.0• .NET Framework 3.5 SP1 must be installed• .NET Framework 3.5 SP1 installed by SQL 2014• DB-Library client tools no longer supported

Other Upgrade ConsiderationsProduct Updates (Slipstreaming) in SQL Server 2014 setup, more info: http://blogs.msdn.com/b/ai/archive/2013/01/14/installing-sql-server-2012-service-pack-1-sp1-cumulative-update-in-one-installation-using-sql-server-2012-product-update.aspx

Upgrade from an Evaluation edition of a previous SQL Server version is not supportedAllowed Upgrade Paths

More info: https://technet.microsoft.com/en-us/library/ms143393.aspx

Other Upgrade Scenarios

Upgrading Both Windows and SQL Server • SQL Server 2014 supports Windows Server 2008 R2 SP1 and Windows Server

2012 and 2012 R2 Server Core • If on Windows Server 2003 or Windows Server 2008, an upgrade of Windows

is required • Before Windows operating system upgrade, install the SQL Service Pack

supported by the upgraded operating system

Upgrading Multiple SQL Instances• Shared components will be upgraded• Backup plan, in case the windows server is inoperative• Backup all databases

Plan for Backups

1. Before upgrade, make a backup of the user databases and data

2. Upgrade complete, perform backups 3. After configuration changes, take full

database backups4. After user acceptance and

validation, take full database backups

Minimizing Upgrade Downtime • Check the legacy SQL Server versions• Make sure that installation requirements are

met• Preinstall .NET and Windows components• Preinstall Visual Studio 2008 SP1 or a later

version• Preinstall SQL Server 2014 common

components• Select the optimal side-by-side upgrade

strategy• Use new service accounts• Check data consistency• Back up data before and after the upgrade

Upgrading Failover Cluster Instances

• Upgrading each node, one at a time• Hardware and software upgrade, do a side-by-

side• Upgrade passive cluster nodes first

• Upgrade at least half of the passive cluster nodes• Stop all traffic for the SQL Server instance, to ensure a

consistent state• Brief outage is required to upgrade

Upgrading AlwaysOn Availability Groups

1. During the upgrade, only back up from the primary replica 2. Prevent unintended failovers, turn off automatic failover to

synchronous-commit replicas 3. Upgrade remote secondary replicas first 4. Upgrade local secondary replicas next 5. Failover the availability group to an upgraded secondary

synchronous-commit replica server6. If failover to an asynchronous-commit secondary replica, data loss

may occur 7. Upgrade the primary replica

Upgrade Assistant for SQL Server 2014 (UAFS) Upgrade Assistant for SQL Server 2014 (UAFS) helps DBA to assess application compatibility and performance difference to upgrade SQL Server from old version to the latest version, download: http://www.scalabilityexperts.com/tools/downloads.html

Step Task Computer SQL Server Version

1 Create a Test Environment Baseline SQL Server 2005/2008/2008R2/2012

2 Capture a Playback Baseline SQL Server 2005/2008/2008R2/2012

3 Setup Playback Baseline System Baseline SQL Server 2005/2008/2008R2/2012

4 Run Upgrade Advisor Baseline SQL Server 2005/2008/2008R2/2012

5 Replay Trace on SQL Server 2005/2008/2008R2/2012

Baseline SQL Server 2005/2008/2008R2/2012

6 Setup Playback Test System Baseline to Test

SQL Server 2005/2008/2008R2/2012

7 Upgrade to SQL Server 2014 Test Upgrade to SQL Server 2014

8 Run Test Trace Playback Test SQL Server 2014

9 Compare and Analyze Test SQL Server 2014

Post Upgrade Considerations

Post Upgrade Considerations

• Checklist • Success Criteria• Jobs• Maintenance Plans• DBCC• Update Statistics• Client strings connections• HA/DR testing• Performance validation

Moving SQL Server to Azure

Moving SQL Server Databases to Azure

• Wizard to deploy DB to SQL Server in Azure VM

• Wizard to deploy DB to Azure SQL Database

SQL Database Migration Wizardhttp://sqlazuremw.codeplex.com/

DemoMoving to Azure SQL DatabaseRoss Loforte

Backup to Azure

Backup to Azure

Managed Backup

• DB on-premise Backup to Azure• SQL Server Backup to URL

• Automated SQL Server Backup Policy• DB on-premise Auto backup to Azure• Agent decides when do backups• Simple configuration• Manage at database level or instance level

Resources

SQL Server 2014 Upgrade Guidehttp://download.microsoft.com/download/7/1/5/715BDFA7-51B6-4D7B-AF17-61E78C7E538F/SQL_Server_2014_Upgrade_technical_guide.pdf

Microsoft Virtual Academyhttp://www.microsoftvirtualacademy.com/

SQL Server 2014 Resources pagehttp://www.microsoft.com/en-us/server-cloud/products/sql-server/Resources.aspx

SQL Database Migration Wizardhttp://sqlazuremw.codeplex.com/

Visit Myignite at http://myignite.microsoft.com or download and use the Ignite Mobile App with the QR code above.

Please evaluate this sessionYour feedback is important to us!

© 2015 Microsoft Corporation. All rights reserved.