none
issues upgrading from 2012 to 2014

    Question

  • We use local copies of SQL Server for development work. Wanting to upgrade from 2012 Express to 2014 Express on my workstation, I downloaded SQLEXPRADV_x64_ENU.exe, ran it, and clicked upgrade from previous version. The upgrade completed with no errors.

    When finished I have a second group of program shortcuts in my start menu. The 2012 config no longer works. When I open the 2014 config it shows the instance as MSSQLSERVER and startup parameters using the same master.mdf as before. If I open Management Studio and select @@version it shows SQL Server 2012.

    Does 2014 still use pieces from 2012? Do I need to remove all 2012 and all 2014, then reinstall from scratch? Thanks

    Tuesday, January 24, 2017 5:27 PM

Answers

All replies

  • Hello,

    That is by design. When you perform an in-place upgrade from one version of SQL Server to a newer version the shortcuts and some programs remain installed (look at Control Panel -> Programs and Features). You can safely remove any program starting with the name SQL Server 2012 from your computer using Control Panel. The new version of SQL Server does not have any dependency on the previous version.

    Hope this helps.



    Regards,

    Alberto Morillo
    SQLCoffee.com



    Tuesday, January 24, 2017 5:36 PM
    Moderator
  • I think something didn't work as it should. You better clearly uninstall 2012 (make sure to completely uninstall) and then you should be able to install the new version.

    But I want to ask - are you sure you want to install SQL 2014 Express version and not SQL 2016 Developer's version?

    The SQL 2016 Developer is free and it is more recent version of SQL Server, so it has more goodies.


    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog


    My TechNet articles

    Tuesday, January 24, 2017 5:42 PM
    Moderator
  • Thanks for the additional info. The project requirements plainly state 2014. I think 2016 would be OK, but I must still to project requirements in case there's an issue.

    I guess I will uninstall 2012, and now 2014, then install from scratch. I can save the databases and reattach afterward.

    Tuesday, January 24, 2017 5:46 PM
  • When I query the server for version it says 2012. If I upgraded, shouldn't it say 2014?
    Tuesday, January 24, 2017 5:47 PM
  • Yes, make sure to have a good backup of all your databases, also you may want to take a disk image before any more work.

    I think clean un-install and then re-install is better.


    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog


    My TechNet articles

    Tuesday, January 24, 2017 5:49 PM
    Moderator
  • Hello,

    Could you please share the Summary.txt log file create by SQL Server setup? The following article will help you locate the file.

    https://msdn.microsoft.com/en-us/library/ms143702(v=sql.120).aspx



    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Marked as answer by dmcdivitt Tuesday, January 24, 2017 8:15 PM
    Tuesday, January 24, 2017 6:28 PM
    Moderator
  • The file Summary.txt was kind of small. Maybe I opened the installer again. I don't see a place to upload files here, so I uploaded them somewhere else.

    Summary.txt

    Summary_D444L40334_20170124_082336_LandingPage.txt

    Summary_D444L40334_20170124_082448.txt

    Summary_D444L40334_20170124_085157_LandingPage.txt

    Summary_D444L40334_20170124_085216.txt

    Tuesday, January 24, 2017 7:36 PM
  • When I looked at the logs I saw some exceptions. When I did the upgrade, it completed quickly. I thought it was a little too quick, but no errors were shown and everything had a green check mark. There was nothing else in the wizard for me to click on, so I had to infer it was done.

    Just now I started setup.exe again from within the install folder. I did it without uninstalling or changing what was done before. I chose upgrade again. Not finished yet, but it's taking a lot longer and doing much more stuff. This time it has "import-export data 64 bit" in addition to "import-export data 32 bit" in the start menu program group. Previously it did not have "import-export data 64 bit".

    Maybe the invoke from the downloaded exe did not happen with correct arguments. Upon clicking the exe it unzips to a folder, then starts after unzipping.

    I will post results when done.


    Tuesday, January 24, 2017 8:05 PM
  • It finished and I queried with @@version. It says 2014. Good!

    Next time I will check the server log as you suggested. I think I will move files to the proper directory and reconfigure accordingly.

    Thanks

    Tuesday, January 24, 2017 8:15 PM
  • Hello,

    I am glad setup did the job on the second run. The first time only LocalDB and SSMS were upgraded.

    Have a great day! Thank you for visiting MSDN forums!



    Regards,

    Alberto Morillo
    SQLCoffee.com


    Tuesday, January 24, 2017 8:25 PM
    Moderator