Share via

What is the difference between new content database and upgraded content database in SharePoint 2016

adil 1,431 Reputation points
2021-01-04T07:11:26.297+00:00

Hi
I want to follow below article to upgrade SharePoint 2013 and SQL 2012 Content database to SharePoint 2016 and SQL 2017
Here my question is after i upgrade is restored database in SharePoint 2016 completely upgraded to SQL 2017 compatibility level ?

what is the difference between if I create new web application with new content database and this upgraded content database?

Microsoft 365 and Office | SharePoint Server | For business
0 comments
Accepted answer
  1. sadomovalex 3,636 Reputation points
    2021-01-05T14:44:48.337+00:00

    upgraded content db may have artifacts (e.g. some old stored procedures or tables if they were not deleted during upgrade process) left from previous SP2013 version which are not used anymore: but in general it's schema will be compatible with SP2016 after upgrade. And of course it will contain content from upgraded web app.
    Content db of web app created in SP2016 will have SP2016 schema (so it will be "cleaner" from this side) but won't have content from SP2013 web app of course.

    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mohamed El-Qassas 1,401 Reputation points MVP Volunteer Moderator
    2021-01-08T08:30:20.23+00:00

    In my answer, I will concentrate on the upgrade part of your question to can get the difference!

    First, you can't upgrade SharePoint in-place, and you must build a new farm so that in the new farm you should create a new web application that by default create a new content database that would hold the new site collection.

    In this case, in the new farm, and once you attach the upgraded content database to the SQL instance, you will need to do the following

    • Dismount the current attached new database content database.
    • Mount the upgraded content database to attach it to the current web application new farm.

    In conclusion, to be able to mount the upgraded database to the new farm, you will need to create a new web application that will create a new content database by default this database is useless in the upgrade process, so you will dismount it then mount the upgraded database for this web application.

    Check the detailed steps to move the content database to a new farm at

    1 person found this answer helpful.
    0 comments
  2. Allen Xu_MSFT 13,866 Reputation points
    2021-01-05T08:04:16.61+00:00

    Hi @adil ,

    Firstly please check the compatibility level values of your databases:
    Go to SQL Server Management Studio -> Right click on your content database -> Properties -> Options:
    53572-1-1.png

    According to this article: ALTER DATABASE (Transact-SQL) Compatibility Level, supported compatibility level values of SQL Server 2017(14.x) include 140,130,120,110,100. As long as compatibility level values of your content databases in SQL Server 2012 is included in these five numbers, it is compatible with SQL Server 2017.

    As to your second doubt, If you create new web application with new content database, The content of your previous web application will not be included in the new web application. As a best practice, I recommend you to test your upgrade process before upgrading. Detailed steps are listed here, please take a reference.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Karen Arul 1 Reputation point
    2021-01-08T07:49:28.717+00:00

    New content database does not have content
    Upgrade content database move old database from one farm to another farm with all sites that hold.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.