This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(41.6, 54%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Hi Team,
We have a requirement to upgrade SQL 2012 SP 1 express to 2017 express edition on multiple machines.
These machines holds Configuration & Transaction Data stored in 2 Databases on each machine.
I have gone through few links which states that SQL 2012 SP 2 express or higher can ONLY be upgraded to 2017 express (refer link below)
It would be great help if anyone can suggest different ways to upgrade without loosing data.
Yes that is correct to upgrade from SQL Server 2012 to SQL Server 2017 the SQL Server should be on Service Pack 2(Sp2) "at least" to allow it for in-place upgrade. If you ask me, since you have SP1, I would suggest you to upgrade to Sp4 and then migrate. This would just fix any bugs at all which you might face.
Hi Shashank,
Thanks for the reply.
So the 2 step process i.e. 2012 SP 1 to 2012 SP 4 and the to 2017 would be the BEST solution as SP 4 would solve all the bugs & compatibility fixes (if any), which would later make easy to upgrade to 2017.
Assuming the Databases will not hampered (we would surely take backup before the process).
Any other solution you can suggest as an option to think of.
We need to find the Best solution with minimal CONS in the upgradation process as we are talking about nearly 1500 machines to be upgraded.
Also if you can share any links for the silent commands to upgrade to 2012 SP 4 & 2017 (using current instance).
If you dont want to do upgrade of current SQL Server 2012 Sp1 to Sp2 or SP4 then you have to build new SQL Server 2017 machines for each new instance to be migrated. Move database by backup and restore and move all logins, jobs and other system wide objects, finally point the application to new machine. The problem is the hostname would change and you would have to change connection strings which if used many places again causes a mammoth task of finding them all. if I were you I would simply upgrade my boxes to Sp4, and do an inplace upgrade. Saves time, save hassle.
I agree with Shanky. Two-step upgrade over SQL 2012 is the way to go.
Also if you can share any links for the silent commands to upgrade to 2012 SP 4 & 2017 (using current instance).
I did some quick googling and found https://learn.microsoft.com/en-us/sql/t-sql/queries/select-for-clause-transact-sql?view=sql-server-ver15. Yes, that is installing, but there should be options for upgrading as well.
I would recommend that you test not only "good" scenarios, but also some ugly ones. With 1500 machines you can count on some surprises, that's for sure!
Thanks Shashank for the reply and details on other options
Thanks for the reply and will check the link for command prompt parameters
Hi Shashank,
Following the 2 step process i have few more queries, it would be great to clear those before i proceed ahead.
SQL Express Edition requires License?
If yes, then does upgrading Service Pack from 1 to 4 require License?
SQL Server express requires NO license. Even for licensed version like Standard and enterprise you do not need any license for SP upgrade. CU and Sp are free
Hi,
The project was delayed due to multiple organizational changes, but we have resumed with the mentioned task again few days back.
Currently we are trying to finalize on the silent commands which can be used to Upgrade SQL 2012 SP1 to SP4 and then to SQL 2017.
While trying to upgrade 2012 SP1 to SP4 i could observe that the EXE does not respond when executed from command prompt (run as administrator) but works fine when EXE is executed directly with Run As Administrator.
SQL Error Log inside temp folder ends with: Setup closed with exit code: 0x84C40013
Setup Bootstrap Log file only generates Global Rules file which shows result as: Passed
I have tried to execute with & without silent commands but the result is same.
Kindly revert if anyone have faced/solved such scenario.
Hello,
The Express Edition is free for use, even in a commercial environment, see Microsoft® SQL Server® Express License Terms for Redistribution and Hosting
Hi,
I was referring to it but was confused with multiple details :)
Thanks for replying
Hi,
The project was delayed due to multiple organizational changes, but we have resumed with the mentioned task again few days back.
Currently we are trying to finalize on the silent commands which can be used to Upgrade SQL 2012 SP1 to SP4 and then to SQL 2017.
While trying to upgrade 2012 SP1 to SP4 i could observe that the EXE does not respond when executed from command prompt (run as administrator) but works fine when EXE is executed directly with Run As Administrator.
SQL Error Log inside temp folder ends with: Setup closed with exit code: 0x84C40013
Setup Bootstrap Log file only generates Global Rules file which shows result as: Passed
I have tried to execute with & without silent commands but the result is same.
Kindly revert if anyone have faced/solved such scenario.
Hi,
The project was delayed due to multiple organizational changes, but we have resumed with the mentioned task again few days back.
Currently we are trying to finalize on the silent commands which can be used to Upgrade SQL 2012 SP1 to SP4 and then to SQL 2017.
While trying to upgrade 2012 SP1 to SP4 i could observe that the EXE does not respond when executed from command prompt (run as administrator) but works fine when EXE is executed directly with Run As Administrator.
SQL Error Log inside temp folder ends with: Setup closed with exit code: 0x84C40013
Setup Bootstrap Log file only generates Global Rules file which shows result as: Passed
I have tried to execute with & without silent commands but the result is same.
Kindly revert if anyone have faced/solved such scenario.