locked
Upgrade: Version of Database not supported or SQL Scripts missing RRS feed

  • Question

  • I'm trying to upgrade a 2014 instance of MDS to 2016. There has also been an edition change in the interim.

    The database was hosted on 2014 Enterprise edition, it is now hosted on 2016 Developer edition.

    The database has still been running 2014 MDS in the interim and now I am turning to the upgrade of MDS and the database itself.

    I have backed up and restored the database to allow me to upgrade alongside the existing database initially for safety reasons! When I select the database in Master Data Services Configuration Manager it tells me that the database version is 12.2.0.0 and needs to be upgraded. On choosing to upgrade the database, the following error occurs;

    "The upgrade from the version of Database is not supported or the SQL scripts for the upgrade are missing"

    I've tried to find information related to this, there are suggestions of bugs in early versions of 2014 but so far haven't found anyone complaining of similar issues with 2016. 

    I have tried a few things to alleviate this;

    • Increased database compatibility to 120, it was set at 100.
    • Changed database owner to the service account configured to run MDS.
    • Increased database compatibility to 130.

    I have attempted with a new database and can get MDS running in 2016 but ideally I want to retain the existing data and not port it to a new instance.

    Can anyone offer any suggestions?

    Thanks and regards

    Justin



    Thursday, January 19, 2017 4:22 PM

Answers

  • Hey Justin ,

    which version of 2016 did you use , please post the version of sql server you tried with .

    Have you used this Cumulative Update ? Sql server 2016 RTM CU4 . please let me know if you face any upgrade issues with this version.

    https://www.microsoft.com/en-us/download/details.aspx?id=53338

    who ever ran into this problem , could you try with this and let me know how it works ?

    thanks,

    santhosh

    Sunday, January 22, 2017 7:39 AM
  • Hi Justin,

    let me clear you one thing , upgrade from 2014 SP2 to 2016 RTM is supported in 2016RTM CU4 only . unless you install CU4 you cannot upgrade Database to 2016 version .

    please confirm , have you used this cumulative Update or not  ? ( the fix is only available here in 2016 RTM CU4)

    https://www.microsoft.com/en-us/download/details.aspx?id=53338

    once you upgrade to 2016 RTM CU4, then you can use 2016 SP1 CU1 to upgrade to SP1 .

    Note: every time we fix the bug it will be released as part of CU Cycle so if you don't apply the exact CU , the link for upgrade will be still broken . so make sure you have right CU and give it a try for upgrade .

    Question : coming to your scenario are you directly trying to upgrade from 2014 sp2 to 2016 SP1 using slipstream ? then upgrade doesn't work currently and we are fixing and once done it will be released in 2016 Sp1 CU2 scheduled on 3/20/2017. so only workaround now is upgrade as below

    2014 SP2 --> 2016 RTM CU4( this is sql version ) once done then upgrade the DB ---> 2016 SP1 CU1 ( upgrade db to sp1 version) .

    please let me know once this is done and if you still face issues , we can discuss this more .

    thanks,

    santhosh

    Wednesday, January 25, 2017 10:14 AM

All replies

  • I literally just experienced the same problem. I think it's SP1. This seems to be a perenial problem going by the search results. 
    Thursday, January 19, 2017 5:47 PM
  • Hey reubster, what architecture are you using?
    Friday, January 20, 2017 10:24 AM
  • Hey Justin ,

    which version of 2016 did you use , please post the version of sql server you tried with .

    Have you used this Cumulative Update ? Sql server 2016 RTM CU4 . please let me know if you face any upgrade issues with this version.

    https://www.microsoft.com/en-us/download/details.aspx?id=53338

    who ever ran into this problem , could you try with this and let me know how it works ?

    thanks,

    santhosh

    Sunday, January 22, 2017 7:39 AM
  • Hi Santhosh, the server is on CU2 so I'm now upgrading to SP1 to check. Will report back...
    Monday, January 23, 2017 10:55 AM
  • Santhosh, I've upgraded to SP1 and still get the same problem.
    Monday, January 23, 2017 11:26 AM
  • To add....I've created a new database to test MDS 2016 initially, that has had to be upgraded as MDS database version was 13.0.13.0. That upgraded successfully to 13.1.0.0.
    Monday, January 23, 2017 11:56 AM
  • that's right, 13.1.0.0 is MDS 2016 SP1 and looks like you have upgraded successfully now . is there any other problem you are facing ? please let me know.

    if anyone is facing the issue , please check my comment and install that version accordingly to avoid any upgrade issues .

    thanks,

    santhosh

    Tuesday, January 24, 2017 6:21 AM
  • Yes I am.

    The database I upgraded to 13.1.0.0 was a blank one created in 2016 CU2 to prove 2016 MDS worked. My 2014 database (which has all our data in), currently version 12.2.0.0 still won't upgrade and still returns the error "the upgrade from the version of the database is not supported or the SQL scripts for the upgrade are missing"



    Tuesday, January 24, 2017 9:40 AM
  • Reubster, I've raised a bug, would be useful if you could tag you can reproduce;

    https://connect.microsoft.com/SQLServer/feedback/details/3119475/master-data-services-2016-upgrade-the-upgrade-from-the-version-of-the-database-is-not-supported-or-the-sql-scripts-for-the-upgrade-are-missing

    Tuesday, January 24, 2017 1:08 PM
  • Hi Justin,

    let me clear you one thing , upgrade from 2014 SP2 to 2016 RTM is supported in 2016RTM CU4 only . unless you install CU4 you cannot upgrade Database to 2016 version .

    please confirm , have you used this cumulative Update or not  ? ( the fix is only available here in 2016 RTM CU4)

    https://www.microsoft.com/en-us/download/details.aspx?id=53338

    once you upgrade to 2016 RTM CU4, then you can use 2016 SP1 CU1 to upgrade to SP1 .

    Note: every time we fix the bug it will be released as part of CU Cycle so if you don't apply the exact CU , the link for upgrade will be still broken . so make sure you have right CU and give it a try for upgrade .

    Question : coming to your scenario are you directly trying to upgrade from 2014 sp2 to 2016 SP1 using slipstream ? then upgrade doesn't work currently and we are fixing and once done it will be released in 2016 Sp1 CU2 scheduled on 3/20/2017. so only workaround now is upgrade as below

    2014 SP2 --> 2016 RTM CU4( this is sql version ) once done then upgrade the DB ---> 2016 SP1 CU1 ( upgrade db to sp1 version) .

    please let me know once this is done and if you still face issues , we can discuss this more .

    thanks,

    santhosh

    Wednesday, January 25, 2017 10:14 AM
  • Santhosh, this is a real can of worms...

    My understanding of SPs was always it included all proceeding CUs so yes I have upgraded from CU2 straight to SP1 consequently missing CU4 along the way. The problem I now face is that I expect I will not be able to apply CU4 to this environment without rolling back from SP1. Furthermore, of the listed fixes in CU4 I cannot see which one specifically fixes my issue?



    Thursday, January 26, 2017 1:20 PM
  • Happy to report I've fixed this though I've had to jump through some hoops to get there! Because I'd upgraded to SP1, I couldn't install CU4 so I've had to commission a separate server to install CU4 on and sure enough upgrade using CU4 then upgrade using SP1 has made the database functional.

    Tuesday, January 31, 2017 9:56 AM
  • Hey reubster, what architecture are you using?

    Sorry, just found your reply. This is a shared, standalone Development server with basically the full SQL Enterprise stack. Windows 2012 on VMWare. 

    Cheers 

    Wednesday, February 1, 2017 4:14 PM
  • Righto. Thanks. 
    Wednesday, February 1, 2017 4:16 PM
  • I can't seem to add a comment but I've upvoted.

    My MDS db is 12.2.0.0 as others here.
    Wednesday, February 1, 2017 4:25 PM
  • Hi Reubster,

    as mentioned in my above comments if you are using sql 2014 SP2 ( which is 12.2.0.0) , we fixed the upgrade support In SQL RTM CU4. please install the SQL 2016 RTM CU4 patch and give a try to upgrade  ( I see JUSTIN  was able to successfully upgrade it after this) .

    sunny

    Wednesday, February 15, 2017 12:10 PM
  • Thanks for confirming. I've got 'my people' on it now. ;-)
    Thursday, February 16, 2017 11:31 AM