SQL Server Upgradation Process

Upgrade Step Description Key Actions

Upgrade Choose the appropriate upgrade method: - In-Place Upgrade: Upgrades the existing
Type in-place or side-by-side. instance.
- Side-by-Side Upgrade: Installs a new instance
and migrates databases.
- Choose based on downtime and complexity.

Pre-Upgrade Perform system checks, backups, and - Verify system requirements for the target
Checklist tests before upgrading SQL Server. SQL Server version.
- Take full backups of all databases (full,
differential, log).
- Test compatibility using SQL Server Data

https://www.sqldbachamps.com
Migration Assistant (DMA).

Hardware/OS Ensure the hardware and OS meet the - Confirm CPU, memory, and storage
Compatibility requirements for the new SQL Server specifications.
version. - Verify OS version compatibility.
- Check whether additional resources
are needed for new features.

Service Pack and Apply the latest service pack or cumulative - Update the existing SQL Server to
Cumulative Updates update for the current SQL Server version the latest service pack or cumulative
before upgrading. update.
- This ensures a smoother upgrade
process and fewer compatibility
issues.
Database Compatibility Verify the database compatibility level for - Identify compatibility level of
Level Check any breaking changes in the new version. databases.
- Plan to upgrade the compatibility
level to leverage new features.
- Use the ALTER DATABASE
command to change compatibility.

System Database Take backups of system databases - Back up system databases manually, as
Backups (master, model, msdb) before the they contain critical configuration settings.
upgrade. - Copy these backups to a safe location.

Disk Space Ensure sufficient disk space for upgrade - Verify available disk space, especially
Availability files, logs, and database growth. for TempDB and log files.
- Clean up unnecessary files before the
upgrade.

https://www.sqldbachamps.com
Stop Maintenance Disable or stop any SQL Server - Disable SQL Server Agent jobs (e.g., backups,
Jobs Agent jobs before starting the index maintenance) during the upgrade process to
upgrade process. avoid conflicts.

Upgrade SQL Perform the actual upgrade using SQL - Use SQL Server Setup (setup.exe) to begin
Server Instance Server Setup Wizard or command-line the upgrade.
tool. - Follow wizard instructions to upgrade
instance, features, and components (e.g.,
SSIS, SSAS, SSRS).

Post-Upgrade Verify the health of the SQL Server instance - Check the SQL Server logs for any
Health Check and databases after the upgrade. errors or warnings.
- Ensure all databases are online and
accessible.
- Test key functionality (queries, jobs,
backups).
Database Update the database compatibility level if - Change compatibility level after
Compatibility Updates required to enable new features or improve confirming the application is
performance. compatible.
- Use the Query Store to monitor the
impact of compatibility changes.

Rebuild Indexes/Update Rebuild indexes and update statistics to - Perform index maintenance on all
Statistics improve query performance on the databases to account for any schema
upgraded system. changes.
- Update statistics using
sp_updatestats or custom
maintenance jobs.

Re-enable Enable or resume SQL Server Agent jobs - Re-enable disabled jobs (backups,
Maintenance Jobs after confirming the system is stable. index rebuilds) and monitor for any
issues.
- Verify that SQL Agent jobs run as
expected post-upgrade.

https://www.sqldbachamps.com
Security and
Permissions Check
Ensure that database security settings, logins,
and permissions are intact after the upgrade.
- Check that logins and users are
properly mapped to databases.
- Ensure permissions are intact for
all roles.
- Test application connectivity and
access.

Post-Upgrade Continuously monitor performance and error - Use SQL Server Profiler or Extended
Monitoring logs for at least a week after the upgrade. Events to track performance.
- Set up monitoring for CPU, memory,
I/O, and query performance.
- Address any post-upgrade issues
promptly.
Backup After Take a fresh full backup of all databases - Perform a full backup of all upgraded
Upgrade once the upgrade has been completed. databases to ensure they are restorable in the
new version.
- Store backups in a secure location.

Documentation and Document the upgrade process, - Create a detailed report of the upgrade,
Reporting issues encountered, and the final including any performance improvements
configuration. and steps for rollback.
- Keep documentation for auditing and future
reference.

Types of SQL Server Upgrades

Upgrade Type Description Advantages Disadvantages

In-Place Upgrades the existing SQL - Less complex, no need to - No rollback option other
Upgrade Server instance to a new migrate databases manually. than restoring from backup.

https://www.sqldbachamps.com
version. - Shorter downtime - Can potentially inherit
compared to side-by-side issues from the old system.
upgrades.

Side-by-Side A new SQL Server instance is - Allows for rollback by - Requires more time and
Upgrade installed alongside the old one, and retaining the old system. resources for setup and
databases are migrated. - Less risk of downtime if migration.
migration is planned - May require additional
properly. hardware or virtual
machines.
SQL Server Version Compatibility

Source Version Target Version (Supported) Upgrade Path

SQL Server SQL Server 2012, SQL Server 2014, SQL Server Direct upgrade supported to newer
2008/R2 2016, SQL Server 2017, SQL Server 2019 versions up to SQL Server 2019.

SQL Server SQL Server 2014, SQL Server 2016, SQL Server Direct upgrade to these versions.
2012 2017, SQL Server 2019, SQL Server 2022

SQL Server SQL Server 2016, SQL Server 2017, SQL Server Direct upgrade to these versions.
2014 2019, SQL Server 2022

SQL Server SQL Server 2017, SQL Server 2019, SQL Server Direct upgrade to these versions.
2016 2022

https://www.sqldbachamps.com
SQL Server
2017
SQL Server 2019, SQL Server 2022 Direct upgrade to SQL Server 2019
and SQL Server 2022.

SQL Server SQL Server 2022 Direct upgrade to SQL Server 2022.
2019
Best Practices for SQL Server Upgrade

Best Practice Details

Test in a Non-Production Always test the upgrade in a development or staging environment before
Environment upgrading the production instance. Ensure all applications work correctly with
the new version.

Back Up Take full backups of all databases, system databases (master, msdb, model), and
Everything configuration files before starting the upgrade.

Use SQL Server Data Migration Analyze database compatibility, feature parity, and performance using
Assistant (DMA) DMA to assess potential issues during the upgrade process.

https://www.sqldbachamps.com
Plan for
Downtime
Communicate the upgrade schedule to stakeholders and plan for sufficient downtime to
accommodate the upgrade and any unforeseen issues.

Monitor Closely After the upgrade, closely monitor performance, error logs, and the functioning of key
Post-Upgrade services for at least a week to ensure everything is running smoothly.

Rollback Plan Have a rollback plan in place (restore backups or revert to the old instance in case of
side-by-side upgrades) in case the upgrade fails or encounters issues.

Summary

This table provides a comprehensive guide to SQL Server upgrades, covering pre-upgrade planning, the actual
upgrade process, and post-upgrade tasks. By following this structured process and best practices, you can ensure
a successful SQL Server upgrade with minimal downtime and risks.