locked
Migration from 2013 to 2019 - Database/setup questions RRS feed

  • Question

  • Greetings,

    We currently have a Sharepoint 2013 environment and have plans to upgrade to 2019 (I understand, there's a step to 2016 in between)

    1.   I have several issues at the moment with space. One of the sites we have, has its own Web Application, and database. However there was a lot of wasted space when the users started dumping and then removing a lot of information over time. This database has unused space that I would love to claim if possibl

    I was wondering if there's a special way of migration that helps me 'migrate' instead of just 'detach, reattach, upgrade' so that I can start with a cleaner/smaller database?

    2 . Another question We have another intranet database that is also growing by the day. At the moment this is one big database with one WebFront End. Would it be smarter to split it up? Is this possible? One of the issues here is that one of the sites had some 3rd party add ons that may not work when migrated. So we'll have to see what happens.

    Thanks in advance for your help.

    Eve

    Tuesday, May 28, 2019 5:48 PM

Answers

  • You will need to shrink the database and is outside of the scope of any database attach migration process. While you can shrink databases, you should avoid doing so as that fragments the indices. You should perform a full reindex post-shrink.

    Note you cannot do a database attach migration from 2013 -> 2019; you need to move to 2016 first, then 2019.

    You can't split a single site collection between multiple databases, but you can add additional data files (NDFs) to a database -- existing data will remain in the current data file but new data will be written to the new data file.

    Here's the info on how to migrate to 2013 -> 2016: https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-to-sharepoint-server-2016

    And 2016 -> 2019: https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-to-sharepoint-server-2019

    You can purchase a 3rd party tool such as Sharegate to do a direct 2013 -> 2019 migration but that has it's own downsides.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by Eve_K Tuesday, May 28, 2019 6:38 PM
    Tuesday, May 28, 2019 6:32 PM

All replies

  • You will need to shrink the database and is outside of the scope of any database attach migration process. While you can shrink databases, you should avoid doing so as that fragments the indices. You should perform a full reindex post-shrink.

    Note you cannot do a database attach migration from 2013 -> 2019; you need to move to 2016 first, then 2019.

    You can't split a single site collection between multiple databases, but you can add additional data files (NDFs) to a database -- existing data will remain in the current data file but new data will be written to the new data file.

    Here's the info on how to migrate to 2013 -> 2016: https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-to-sharepoint-server-2016

    And 2016 -> 2019: https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-to-sharepoint-server-2019

    You can purchase a 3rd party tool such as Sharegate to do a direct 2013 -> 2019 migration but that has it's own downsides.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by Eve_K Tuesday, May 28, 2019 6:38 PM
    Tuesday, May 28, 2019 6:32 PM
  • Thank you.

    I will read up on having additional data files. I appreciate your help!

    Tuesday, May 28, 2019 6:38 PM