Post reply

SQL 2017 to SQL 2025. Good to Go ?

  • April 8, 2026 at 4:17 pm

    #4763053

    We need to replace our Windows server running SQL 2017. Any reason not to go to SQL 2025 ?  Any "gotchas" migrating databases from SQL 2017 to SQL 2025 ?

  • April 8, 2026 at 9:16 pm

    #4763173

    There shouldn't be an issue with that big of a leap in faith.

    The only things to watch out for are the upgraded encryption defaults. If apps accessing the database are using the old encryption TLS 1.2 and below, there will be an issue.

    Also, server connections will use encryption by default so you'll need to ensure your certificates aren't expired and possibly may have to switch drivers.  I believe SQL Native Client has been deprecated or not supported in 2025 so you'll have to switch to MS OLE DB Driver for SQL Server

    I'd run a sql server upgrade assessment first to work out the bugs before applying an upgrade.  And always make sure to back your system databases as well in case you need to rollback.  Hopefully they won't be needed.

    Tung Dang
    Azure and SQL Server DBA Contractor / Consultant
    SQL Brainbox - SQL Server Monitoring Tool

  • April 9, 2026 at 1:27 pm

    #4763463

    Thanks. We aren't using encryption on anything.

  • April 9, 2026 at 4:57 pm

    #4763545

    My only bit of advice would be to do this on a TEST system first and get testing done on all impacted applications before cutover. Also have a post migration test plan that you can run through to make sure things are "up" that should be up and you can say it was a successful upgrade.

    You don't want to do the upgrade on Saturday and have the company down Monday morning.

    If you are doing a migration upgrade (not in place upgrade) also make sure to re-map all users to logins after you are complete. Not always required, but I've been hit by that before.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • April 10, 2026 at 1:36 pm

    #4763970

    Thanks for the tips. I have been away from DBA work for a while so I will have to dust off my notes !

    • This reply was modified 1 weeks, 2 days ago by homebrew01.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply