Post reply

Take Backup from SS 2017 to Older Version

  • June 25, 2018 at 7:26 am

    #363731

    I support a production database that was recently migrated to SS 2017. For years I have taken backups of that database and restored them to a different server/database (SS 2016) as a development instance. I don't do a lot of serious development on it, it's just there to validate minor changes in a more convenient location. I have another, parallel database on the 2017 sever for full development work, but it's not so much fun to get to. 

    Now I find that I can't restore the 2017 backup to the 2016 instance. I understand the reasons for that--changes in internals that are not compatible between versions.
    Short of installing 2017 on my backup/development server, are there any practical options available? I looked at scripting it, but that seems not to be particularly efficient, :).

    If there is no alternative, I'll bite the bullet and install yet another local instance (probably SS 2017 Express or Developer, actually, because all I really need is a place to validate changes for development.) But it seems like there ought to be a middle-ground that doesn't require proliferating instances to monitor.

    Thanks in advance.

    George Hepworth

  • June 25, 2018 at 7:35 am

    #1995152

    I forgot to mention that I'm lazy.

  • June 25, 2018 at 8:07 am

    #1995156

    I don't know if it will work, but I would give the "copy database" wizard from SSMS a try (right-click a database...tasks...copy database). If that don't work you can still use the import/export wizard as long as the structure remains unchanged 😉

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • June 25, 2018 at 8:14 am

    #1995158

    Unfortunately, you've already covered your two options.
    Either script out the tables, data, etc, or install a SQL2017 instance (I'd recommend Developer edition, it's free and you don't have the 10GB database size limit to worry about.)

  • June 25, 2018 at 8:19 am

    #1995159

    Okay, thanks. I am both lazy and a firm believer in miracles. That often combination often leads to disappointment, I'm afraid.

  • June 25, 2018 at 9:58 am

    #1995175

    Was there a reason you couldn't upgrade the development server to 2017?  Typically you'd want to upgrade the development server before upgrading the production server so the system could be tested and verified with the upgrade.

  • June 25, 2018 at 10:07 am

    #1995176

    George Hepworth - Monday, June 25, 2018 8:19 AM

    Okay, thanks. I am both lazy and a firm believer in miracles. That often combination often leads to disappointment, I'm afraid.

    Going to be honest, that miracle isn't going to happen. You haven't been able to restore backwards since, well ever.

    Perhaps it's time, instead, to change the work ethic. 🙂

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • June 25, 2018 at 10:09 am

    #1995177

    See my previous reply.

    I upgraded here just now. It was already upgraded on the customer's site for both dev and production, so this is mostly for my convenience when I don't want to RDP in to their side to check things out.

Viewing 8 posts - 1 through 7 (of 7 total)

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