SQL Server 2005/8/R2 Instance SQL Server 2014 Instance

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

Compare and Verify SQL Server 2005/8/R2/2012 Instance SQL Server 2014 Instance Verified!

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

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 3 rd 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”

1. Before upgrade, make a backup of the user databases and data 2. Upgrade complete, perform backups 3. After configuration changes, take full database backups 4. After user acceptance and validation, take full database backups

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 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

StepTaskComputerSQL Server Version 1Create a Test EnvironmentBaselineSQL Server 2005/2008/2008R2/2012 2Capture a PlaybackBaselineSQL Server 2005/2008/2008R2/2012 3Setup Playback Baseline SystemBaselineSQL Server 2005/2008/2008R2/2012 4Run Upgrade AdvisorBaselineSQL Server 2005/2008/2008R2/2012 5Replay Trace on SQL Server 2005/2008/2008R2/2012 BaselineSQL Server 2005/2008/2008R2/2012 6Setup Playback Test SystemBaseline to TestSQL Server 2005/2008/2008R2/2012 7Upgrade to SQL Server 2014TestUpgrade to SQL Server Run Test Trace PlaybackTestSQL Server Compare and AnalyzeTestSQL Server 2014

Wizard to deploy DB to SQL Server in Azure VM Wizard to deploy DB to Azure SQL Database

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