Microsoft

SQL Server Upgrade Paths for Older Business Databases

Database administrator planning a SQL Server migration with documentation and server equipment

A SQL Server upgrade from older versions is not simply a matter of installing a newer setup file. The database may support a business application, reporting system, integration service or custom software that was built around a particular SQL Server release. The target version must therefore fit the application, operating system, backup process, security model and licensing arrangement.

This is especially important for organisations still running SQL Server 2014 or SQL Server 2016. A carefully planned upgrade can centralise business data on a supported, maintainable platform while reducing avoidable disruption. A rushed upgrade can produce compatibility errors, missing drivers, failed reports or an unexpected requirement for additional access licences.

Start with an inventory of the current SQL Server environment

Before selecting SQL Server 2019, SQL Server 2022 or SQL Server 2025, record what is actually running. An organisation may believe it has one database server but in practice have several instances, development systems, reporting replicas, test databases and application-specific installations.

  • SQL Server version and edition: record the release, edition, build, instance name and whether the installation is Standard, Express, Developer or another edition.
  • Database inventory: list production, reporting, staging and test databases, including their size, growth rate, recovery model and business owner.
  • Applications: identify the ERP, CRM, warehouse, accounting, document management and line-of-business applications connected to each database.
  • Integrations: document imports, exports, APIs, scheduled jobs, ETL processes, linked servers, reporting connections and third-party connectors.
  • Operational dependencies: note backup software, monitoring, maintenance jobs, antivirus exclusions, virtualisation, storage and disaster recovery procedures.
  • Access model: count people and devices that access the SQL Server environment through applications, reports or direct connections.

Also identify the server operating system and the hardware or virtual machine resources. A database migration can expose storage or memory limitations that were hidden by the older workload. Capacity planning should use measured CPU, memory, disk latency, database growth and peak query activity rather than a general assumption that a newer version will solve performance problems.

Assess compatibility before choosing an upgrade method

Compatibility has two parts. The first is whether the database can be moved to the target SQL Server release. The second is whether the application and its drivers continue to work after the move.

Ask the software supplier which SQL Server versions and editions are supported. This applies to commercial applications as well as custom systems. A database may restore successfully on a newer server while the application still fails because of an outdated provider, connection string, reporting component, authentication setting or unsupported database feature.

Review the following areas during assessment:

  • Database compatibility level: a newer SQL Server instance may allow a database to retain a previous compatibility level during testing. This can help separate the server migration from later application or query changes, but it is not a substitute for full validation.
  • Deprecated or changed behaviour: inspect older syntax, configuration settings, authentication methods, jobs and features that the target version may handle differently.
  • Drivers and client tools: check ODBC, OLE DB, JDBC, .NET providers, reporting tools and administration software on every connected system.
  • Collation and language: verify sorting, comparison, accent handling and date or number processing where the database serves multilingual European users.
  • Security: test Windows or Microsoft Entra-related authentication where used, database roles, service accounts, encryption, certificates and least-privilege access.
  • SQL Agent and automation: migrate and test jobs, alerts, operators, maintenance plans and scripts rather than assuming they will behave identically.

Use a representative copy of the production databases. Test the most important transactions, not only a successful login. For example, an accounting system should be tested for posting, period reporting and exports; a warehouse system should be tested for stock movements, order allocation and label generation.

SQL Server 2014 upgrade and SQL Server 2016 upgrade options

A SQL Server 2014 upgrade or SQL Server 2016 upgrade normally starts with a decision between an in-place upgrade and a side-by-side migration.

Approach Jak to funguje Nejvhodnější pro Main risks
In-place upgrade The existing SQL Server installation is upgraded on the same server. Small, well-documented environments with compatible applications and a practical rollback plan. Less separation between old and new systems; rollback and troubleshooting can be more difficult.
Side-by-side migration A new SQL Server instance or server is prepared and databases, logins, jobs and integrations are moved to it. Business-critical systems, older operating systems, hardware refreshes and environments needing a controlled fallback. More planning; dependencies can be missed if the inventory is incomplete.
Staged migration Non-production systems or selected databases move first, followed by production after validation. Organisations with several applications or a need to reduce change risk. Temporary coexistence may require additional administration and licensing review.

For an older production database, side-by-side migration is often easier to control because the original environment can remain available while the new environment is tested. It also provides a natural opportunity to review storage, backups, monitoring, service accounts and security instead of carrying every historic configuration into the new installation.

Do not assume that every old database can be restored directly to every newer target. Confirm the supported route for the source and target releases, and use an intermediate step or a data migration method when Microsoft or the application supplier requires one.

Choosing SQL Server 2019, 2022 or 2025

The right target is not automatically the newest release. It should be the version that combines a suitable support position, application compatibility, operational readiness and a licensing model the organisation can administer.

Target When it may fit What to verify Doporučení
SQL Server 2019 A conservative target for an application supplier or internal team that has already validated this release. Application support, operating system requirements, security configuration and the remaining maintenance horizon relevant to the organisation. Choose it when compatibility evidence is stronger than for newer targets and there is a clear reason not to move further.
SQL Server 2022 A modern target for operational databases, reporting workloads and structured business data in a managed Microsoft database environment. Application and driver support, migration tooling, backup compatibility, performance baselines and licensing requirements. Use it as a balanced target when the business wants a current platform and its applications are validated for the release.
SQL Server 2025 A current target for organisations planning a new Microsoft SQL Server Standard deployment or a longer-term platform decision. Application certification, operating system compatibility, supplier support, internal skills, testing effort and the applicable Microsoft licensing terms. Consider it for new or fully validated environments; do not select it solely because it is the newest option.

SQL Server 2022 Standard is designed for organisations that need a central relational platform for operational applications, reporting and controlled data storage. SQL Server 2025 Standard provides the same broad type of foundation for managed SQL workloads, with the product designation and licensing requirements needing to match the planned deployment.

For a SQL Server 2014 upgrade or SQL Server 2016 upgrade, compare the target against the application supplier’s support matrix before scheduling the change. If an application is certified only for a particular release, that technical constraint can outweigh the attraction of a newer target. Conversely, choosing an old target only to avoid testing may create another upgrade project sooner than necessary.

Technician validating server connections during a database migration

Keep server and CAL licensing in the same conversation

Database licensing should be reviewed before the technical design is final. The number of servers alone does not describe the licensing requirement. Consider the SQL Server edition, deployment architecture, access method, users, devices, test environments and any existing Microsoft agreement or licence entitlement.

Where a Server plus CAL model applies, the organisation normally needs the SQL Server server licence together with the relevant SQL Server CALs for users or devices accessing the server. The correct choice depends on how people and equipment connect to the database. A User CAL may suit a defined person using several devices, while a Device CAL may suit a shared workstation or terminal used by several people. Confirm the applicable Microsoft terms for the selected product and scenario before ordering.

Count indirect access carefully. Employees may reach SQL Server through an ERP system, web application, reporting platform or service rather than opening a database tool directly. Those access patterns still need to be assessed under the licensing model being used. External users, contractors, multiplexing, virtual machines, backup servers and development or test systems may also require specific treatment.

SQL Server 2025 Standard is available as a standalone product, and a SQL Server 2025 Standard plus 10 CALs product is also available from KEYFORREST. The bundle includes ten SQL Server 2025 Standard CALs, with User CALs supplied by default; ask at checkout if Device CALs are needed. Review the current product page and your licensing requirements before selecting a bundle. Genuine licences are available at KEYFORREST with instant electronic delivery.

Do not infer that a 2025 licence automatically covers an older server, every database instance or every connected user. Licence rights can depend on the exact edition, agreement and deployment. If your organisation has volume licensing, subscription rights, Software Assurance or a complex virtualised design, confirm the position with Microsoft or an authorised licensing adviser.

Back up, migrate, test and validate

A reliable migration plan includes a tested recovery route. A backup that has never been restored is not enough evidence that the business can recover.

  1. Document the baseline: record database sizes, normal transaction times, scheduled jobs, reports, integrations, user roles and peak workload behaviour.
  2. Prepare the target: install the selected SQL Server edition on supported infrastructure, apply the required updates, configure storage and set up monitoring, security and backup destinations.
  3. Protect the source: take verified full and transaction-log backups where applicable, record the recovery point and agree a change freeze or final synchronisation procedure.
  4. Migrate a copy: restore or transfer representative databases, then move logins, permissions, jobs, certificates, linked services and application configuration as appropriate.
  5. Run functional tests: test user login, inserts, updates, searches, reports, imports, exports, scheduled processes and integrations. Include multilingual data and business-critical edge cases.
  6. Run technical tests: compare query performance, backup and restore, failover or recovery procedures, storage usage, monitoring alerts and maintenance tasks.
  7. Complete a controlled cutover: communicate downtime or restricted access, stop writes if required, perform the final migration, update connection settings and monitor the first production workload closely.
  8. Keep a rollback plan: define the conditions for returning to the source system, who approves that decision and how new transactions will be reconciled.

After cutover, do not immediately raise the database compatibility level or change several performance settings at once. First establish that the application works on the new instance. Then make controlled changes, measure the result and keep a record of what was changed.

Which path fits your organisation?

  • Small business with one stable application: inventory the installation, verify supplier support, test a side-by-side migration and choose the simplest compliant licensing model.
  • Several applications on SQL Server 2014 or 2016: migrate a test system first, group applications by dependency and avoid one large untested cutover.
  • Business with an application supplier constraint: use the certified target even if it is not the newest release, then schedule a future upgrade based on the supplier roadmap.
  • Organisation replacing hardware or virtual machines: prefer a side-by-side design so storage, backups, security and monitoring can be rebuilt and verified independently.
  • Growing user or device base: model access before purchase and compare User CAL and Device CAL requirements rather than estimating from database size alone.

Často kladené otázky

Can I upgrade SQL Server 2014 directly to SQL Server 2022 or 2025?

The supported route depends on the source edition, target edition, database features, operating system and application. Verify the exact upgrade or migration path in current Microsoft and application documentation before proceeding.

Is an in-place upgrade better than a side-by-side migration?

Neither is universally better. In-place work can be simpler for a small, well-tested installation. Side-by-side migration usually gives more control for critical systems, hardware changes and rollback planning.

Should every organisation choose SQL Server 2025?

No. SQL Server 2025 may be appropriate for a new or fully validated deployment, but application certification, operating system support, internal skills and licensing must be checked first.

Do application users need SQL Server CALs if they never open SQL Server Management Studio?

Possibly. Access through an application, report or service still needs to be assessed under the selected licensing model. Review indirect access and the applicable Microsoft terms.

What should I test after the migration?

Test business transactions, reports, integrations, permissions, scheduled jobs, backups, restores, performance and recovery procedures. A successful database restore alone does not validate the complete application.

author-avatar

O autorovi Marios Chaidousis

Marios Chaidousis je specialista na software a licence se zaměřením na Autodesk (AutoCAD, Revit, Inventor), Microsoft (Office, Microsoft 365, Windows, Windows Server, SQL Server), Adobe a bezpečnostní software. Pomáhá inženýrům, profesionálům a firmám vybrat správnou licenci a využít software naplno.LinkedIn · Facebook · Instagram