Blog
SQL Server Upgrade Planning: Versions, CALs and Testing
SQL Server upgrade planning should begin before anyone runs the setup program. A database server can support an ERP system, a line-of-business application, reporting, backups, integrations and scheduled jobs at the same time. Changing its version without mapping those dependencies can cause application errors, failed reports or an avoidable service outage.
The licensing side also needs attention. A technical migration may appear successful while users or devices no longer have the correct access licensing for the target SQL Server edition. The safest approach combines an inventory, compatibility testing, a documented recovery plan and a review of how people and devices access the database.
This guide is designed for IT administrators and managed service providers planning a SQL Server 2019 to 2025 upgrade or another version transition. Treat the version path, edition rights and access requirements as items to confirm against the current Microsoft documentation and your licensing agreement.
1. Build a complete SQL Server inventory
Start with facts rather than assumptions. Record every SQL Server installation, including servers that are not visible in the main production environment. Small departmental instances, application appliances, development servers and reporting copies can be missed during a normal asset review.
For each instance, record:
- SQL Server version, edition, build and service pack or cumulative update level
- Windows Server version, virtual machine or physical host, CPU, memory and storage layout
- Instance name, ports, service accounts and authentication configuration
- Database names, sizes, recovery models, compatibility levels and encryption settings
- SQL Server Agent jobs, maintenance plans, linked servers, credentials and operators
- Integration, reporting, analysis or replication components in use
- Backup destinations, retention, restore-test results and monitoring coverage
- Applications, scripts, reports and integrations that connect to each database
- Business owner, technical owner, support contact and permitted maintenance window
Ask application owners how their software connects. A connection string may refer to an instance name, a fixed port, an alias or a DNS record. An upgrade that changes the server name, instance name or network path can therefore break an application even when the databases themselves restore correctly.
Also map indirect access. An employee may use a web application, remote desktop session, reporting tool or service that connects to SQL Server on their behalf. Document the user or device population behind those services rather than counting only the accounts visible in SQL Server.
2. Check compatibility and edition requirements
Before selecting an upgrade method, compare the current environment with the target SQL Server edition. SQL Server 2025 Standard is intended to provide a controlled Microsoft server database platform for storing, organizing, querying and managing structured business data. Whether it is suitable depends on the workload, required capabilities, capacity, high-availability design and application support requirements.
Review the following areas with the application vendor or internal development team:
- Supported SQL Server versions and Windows Server combinations
- Database compatibility level and any deprecated or changed behavior
- Transact-SQL code, stored procedures, triggers and functions
- Drivers, providers, client libraries and connection encryption settings
- Collation, language, date, time-zone and sorting assumptions
- SQL Server Agent jobs, linked servers, external integrations and credentials
- Reporting, integration and analytics components used with the application
- Database size, transaction volume, peak concurrency and storage performance
Do not equate a successful database restore with application compatibility. A restore proves that the database can be transferred to the target environment; it does not prove that every query, report, scheduled job or interface behaves as expected.
For a SQL Server 2019 to 2025 upgrade, confirm the supported route for each instance. Depending on the source edition, target edition, application constraints and operational requirements, an in-place upgrade may not be the best or even an available option. A side-by-side migration can provide better control, but it requires a plan for moving databases, logins, jobs, certificates, integrations and client connections.
3. Use a SQL Server version upgrade checklist
A written checklist turns a complex change into verifiable controls. The following structure works for both a single business server and a managed service provider handling several customer environments.
| Stage | Checks to complete | Evidence to retain |
|---|---|---|
| Discovery | Instances, databases, applications, owners, integrations and access paths are recorded. | Inventory export, dependency map and application contact list |
| Assessment | Target edition, operating system, compatibility, capacity and vendor support are reviewed. | Assessment notes, exceptions and remediation actions |
| Preparation | Backups, monitoring, installation media, service accounts and change approvals are ready. | Backup reports, configuration files and approved change record |
| Testing | Representative databases and application workflows are tested on the target build. | Test scripts, timings, defect log and sign-off |
| Migration | Runbook, outage window, communication plan and rollback decision points are agreed. | Execution log and time-stamped validation results |
| Closure | Applications, jobs, backups, monitoring, permissions and licensing records are validated. | Acceptance record, updated inventory and support handover |
4. Protect backups and define rollback
Backups are only useful when they can be restored. Before the change, take and verify current full backups, transaction log backups where applicable, system database backups and backups of encryption keys or certificates required to read protected data. Preserve a copy in a location that remains available if the source server has to be isolated or rebuilt.
Perform a test restore on the target environment. Check database consistency, expected recovery point, permissions and the time required to restore a realistic database. For larger systems, measure the full recovery sequence rather than relying on a small test database.
Define rollback before the maintenance window starts. A rollback plan should state:
- What event causes the team to stop or reverse the migration
- Who has authority to make that decision
- How application connections will return to the previous instance
- How new transactions will be handled if both systems have been active
- How DNS, aliases, load balancers, firewall rules and scheduled jobs will be restored
- How users and application owners will be informed
An in-place upgrade and a side-by-side migration have different rollback characteristics. With an in-place change, the original environment is modified directly. With a side-by-side approach, the old instance can often remain available during preparation, but data synchronization and the final cutover must be carefully controlled. Do not describe a backup as a rollback plan unless the restore process, downtime and data-loss position are understood.
5. Test applications, not just databases
Create a test environment that resembles production closely enough to expose real issues. Use a copy or representative subset of each important database, while protecting personal and confidential information. Where possible, reproduce the target operating system, SQL Server edition, configuration, network rules and authentication method.
Test normal workflows first: sign-in, record creation, updates, searches, document handling, order processing, financial operations and other actions that matter to the business. Then test scheduled and less visible functions:
- Nightly jobs, maintenance tasks and index or statistics operations
- Reports, exports, dashboards and automated email delivery
- Imports from files, line-of-business systems or external services
- Linked-server queries and cross-database procedures
- Application failover or service restart behavior
- Backup, restore and monitoring alerts
- Performance during representative concurrent activity
Capture baseline timings before the upgrade. Compare query duration, application response time, CPU, memory, storage latency, blocking and failed job counts after the migration. A version change can expose inefficient queries or configuration differences that were not visible in a short functional test.
Ask each application owner to approve a short acceptance script. A test is not complete because the database administrator can connect; it is complete when the people responsible for the business process confirm that the process works.
6. Review SQL Server CAL licensing and access
Technical access and licensing access are related but not identical. SQL Server CAL licensing should be reviewed at the same time as the upgrade so that the target environment is covered when users return to production.
For SQL Server 2025 Standard, a Client Access Licence is required for every user or device that accesses SQL Server 2025 Standard. A User CAL covers one person using any number of devices. A Device CAL covers one device used by any number of users. The SQL Server 2025 Standard CAL product supports either type, and the quantity should match the access model documented for the environment.
| Access model | Usually fits when | Review carefully |
|---|---|---|
| CAL utilisateur | The same named people use SQL Server from multiple computers, tablets or other devices. | Leavers, contractors, shared accounts and service users |
| CAL appareil | Several shifts or people use a defined set of workstations or terminals. | Remote access, replacement devices and unmanaged endpoints |
| Application or service access | Users reach SQL Server through an application, portal, RDS session or reporting service. | Indirect access, multiplexing and the licensing terms that apply to the deployment |
Do not count only the SQL logins visible in a management tool. Include application users, service workflows, reporting connections, remote desktop environments and devices that reach the database indirectly. Exchange, SharePoint, RDS and other Microsoft workloads may have separate licensing requirements; a SQL Server CAL does not replace the access licensing for those products.
When upgrading SQL Server, check whether existing CALs cover the target version under the organization’s agreement and whether Software Assurance or other rights affect the position. Do not assume that a previous SQL Server CAL automatically covers a newer server version. Keep the purchase record, CAL type, quantity, version and allocation method with the licensing documentation.
SQL Server 2025 Standard CALs are available as User or Device CALs. They are supplied digitally by email, and the current product page shows the available purchasing details. For complex environments involving external users, shared services, virtualization or indirect access, confirm the model with Microsoft or a qualified licensing adviser.
7. Choose the migration method
Choose the method after the assessment and testing work, not before. An in-place upgrade can reduce the number of moving parts, but it changes the existing server and may make a rapid return to the old state difficult. It also requires careful checks for installed components, disk space, service accounts and application dependencies.
A side-by-side migration installs the target SQL Server separately and moves databases and supporting configuration. It is often easier to test in advance and can provide a clearer cutover point. Its extra work includes transferring logins and permissions, SQL Agent jobs, linked servers, certificates, connection aliases, firewall rules, monitoring and backup configuration.
Other approaches may be appropriate for large or highly available systems, including staged data movement or a planned replica and cutover. The correct choice depends on downtime tolerance, database size, recovery objectives, application behavior and the capabilities supported by the target design.
Write the runbook in execution order. Include pre-change checks, backups, migration commands or tools, connection changes, smoke tests, business acceptance, monitoring and rollback triggers. Assign one owner to each step and record the expected duration.
8. Validate the production environment after cutover
Post-upgrade validation should continue beyond the first successful connection. Confirm that every production application connects to the intended instance and that users can complete their normal tasks. Check database status, compatibility settings, permissions, encrypted connections, SQL Server Agent jobs and linked services.
Verify that backup jobs run on the new server and that monitoring detects service failure, storage pressure, failed jobs and unusual performance. Review the first complete backup and, where practical, perform another restore test after the configuration has stabilized.
Compare the new server with the approved baseline. Look for unexpected changes in query duration, blocking, CPU, memory, storage latency, failed logins and application errors. Keep the old environment protected until the agreed retention and rollback period has passed, but do not leave obsolete services, accounts or firewall rules active indefinitely.
Finally, update the asset inventory, diagrams, disaster recovery documentation, support procedures and licensing records. A managed service provider should also update the customer’s configuration database and close any exceptions identified during testing.
Foire aux questions
Is a direct SQL Server 2019 to 2025 upgrade always possible?
No. The supported route depends on the source edition, target edition, operating system, installed components and application support. Confirm the route before choosing an in-place upgrade; a side-by-side migration may provide better control.
Can a database restore prove that an upgrade is safe?
No. A restore confirms that the database can be moved, but application workflows, reports, jobs, integrations, drivers and performance still need testing.
Should I choose User CALs or Device CALs?
Choose User CALs when named people use multiple devices. Choose Device CALs when several people share defined devices. Include indirect access and review the actual deployment before deciding.
Do SQL Server CALs cover RDS, Exchange or SharePoint access?
No. SQL Server CALs address access to the relevant SQL Server deployment. RDS, Exchange, SharePoint and other Microsoft products can have separate licensing requirements.
Where can I obtain SQL Server 2025 Standard and CALs?
Genuine SQL Server 2025 Standard licences and SQL Server 2025 Standard User or Device CALs are available from KEYFORREST with instant electronic delivery. Check the current product page for the available purchasing details and select the CAL type and quantity that match your reviewed access model.