This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
How does one migrate system databases from an old SQL Server 2012 to a new SQL Server 2017?
Some general info found here.
https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
--please don't forget to Accept as answer if the reply is helpful--
Thank you DSPatrick - I will read the information.
Hi John-4691,
Suggest you upgrade SQL server 2012 to SQL server 2017, but you need to apply SP4 for SQL server 2012 before directly upgrading SQL server 2012 to SQL 2017. Because SQL Server 2017 (14.x) supports upgrade from SQL Server 2012 SP2 or later, refer to MS document. You can follow the steps from this document Upgrade SQL Server Using the Installation Wizard (Setup).
We can’t not move SQL server 2012 system databases to SQL server 2017. We can only move the system database between same version. Moving system database not recommended for database installation its ideal for troubleshooting & disaster recovery purposes . For migrating system database, please refer to Move System Databases.
===============================================
Best regards,
Cathy
If the response helped, do "Accept Answer" and upvote it.
@CathyJi-MSFT - What we have is an old SQL Server 2012 cluster that we are migrating to a SQL Server 2017 cluster. Right now, I have not installed SQL 2017 on the new cluster (but I was about to until I read this). It sounds like I must install SQL 2012 on the new cluster, backup all of the databases on the old SQL Server 2012 cluster, restore all databases on the new cluster, and then upgrade the new cluster to SQL 2017. Is that right? That seems like a "vacuum tube technology" process if true. I cannot believe there isn't a better way. Either way, thank you for your response.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 40%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENC%3C/text%3E%3C/svg%3E)
I wonder if you can shorten your downtime by logshipping your data to the new server or just during the cut over have an "upgraded" copy of your SQL Server using the method documented here ready to go, but just have stale data... "backup of current day" before your cutover the current day... at the "outage window" try to backup the trans log - as there should be LESS trans log since your full backup and apply it to the new server so the down time is shorter. I wonder if the translog formats from old version to new are same or can recognize it to upgrade the logs and apply to your new server. Then you have a shorter down time and you and just switch your host entries?
I would test this but this could shorten your outage window.
Hello,
You cannot migrate system databases from lower to higher version and vice versa. The option to migrate from lower to higher version is only available for "user" databases. For objects stored in system databases like jobs, logins and packages you need to script out and create it on destination machine. Let me know if you need help with that.
/Shanky
*anonymous user*621 - Yes, as indicated above in my reply to Cathy, we are migrating from a SQL Server 2012 cluster (with several named instances as well as the default instance) to a SQL Server 2017 cluster. Due to another matter that cropped up, I haven't installed SQL on the new cluster (but I do have the underlying fail-over clustering installed, configured, and tested with a good validation). If there is a way to COMPLETELY transfer all information such as security logins, jobs, and packages over to the new cluster, I am all for it. I really don't need to move the system databases (nor do I want to). What prompted me to ask my silly question is that I've read many articles where someone ran a script that isn't complete. Although I have been maintaining this existing cluster for many years (yes, I inherited it), this is my first attempt to migrate from one version/old platform to a newer version/new platform. I'd like to get it right.
@John This is not a silly question, lot of people have the same dilemma as you have. I have done countless migrations and transferring jobs, packages, logins and server objects can be done very easily. Let me know if you need links to do it
@Shashank Singh - Yes, I would be interested in learning more.