Report copy of 2008R2 on 2017

  • paul.doherty

    SSC Enthusiast

    Points: 196

    Hi all ,

     

    we have a proprietry 2008R2 Standard OLTP db which is on 2008R2 and at the moment cannot be moved. Eventually we will have a DW type solution, but we are not there yet. But we need to quickly get away from reporting off the live data.

    We have a copy and restore to a 2017 Enterprise instance. Which in the interim we are hoping to report off.

    The restore works fine are there other things we need to do to take advantage of the new server.

    Compatability level - can we just change this?

    Index fragmentation should be basically handled on the 2008 live db. Of course it wont be optimised for reporting on 2017 - but the new version shouldn't require a reorder/rebuild?

    My understanding is - statistics will need updating as

    https://www.sqlskills.com/blogs/erin/do-you-need-to-update-statistics-after-an-upgrade/

    Will we be better setting the database as read only too.

     

    Obviously not an ideal solution - but any advice would be very welcome! Thanks

    Paul

  • Site Owners

    SSC Guru

    Points: 80385

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 2 (of 2 total)

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