Migrating database from old SQL & Windows Server to new SQL Server Edition

EnterpriseArchitect 6,161 Reputation points
2025-07-18T05:55:06.9133333+00:00

I plan to deploy the latest version of Windows Server 2025 alongside SQL Server 2024 Standard Edition.

What are the recommended approaches and the sequence of steps for performing the migration with minimal downtime, if possible?

When migrating a database VM that is currently running an outdated and unsupported SQL Server 2005 on a Windows Server 2008 VM hosted on VMware, what method should we use to ensure that the application remains connected to the database server without making drastic changes? Do I need to configure the migrated SQL Database using the detach and attach method while ensuring compatibility mode and the same collation, as well as maintaining the same IP address?

SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Erland Sommarskog 124.2K Reputation points MVP Volunteer Moderator
    2025-07-18T08:28:41.33+00:00

    First, there is no SQL Server 2024. The current in-market version is SQL Server 2022. SQL Server 2025 is in preview, expected to be release before the year ends.

    The best approach to move the database is by BACKUP/RESTORE. Testing is essential. The lowest compatibility level supported is 100, that is the level of SQL 2008. Furthermore, some older features have been dropped entirely, so if you are using any of them, you will have some work to do.

    I would recommend that you aim for compatibility level 160, that is the most recent. This can have some repercussions for performance, which you may or may not find during testing. But you should test with compat level 160. You should also enable Query Store the first thing you do.

    Once you have completed testing, you can start thinking on how to do the actual cutover. But one tip for performance: Again, enable Query Store first thing. But stay at compat level 100 for two weeks. Then switch to compat level 160. If you get performance regressions, you can force the old plan with help of Query Store to solve the urgent problem, while you are working on a long-time solution.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.