Thursday, April 17, 2014

SharePoint 2013: How to migrate the metadata database

Introduction

This posting walks you through the process of migrating the metadata database, from a 2010 farm to a 2013 farm.  This migration is performed prior to migration of the content databases.

Preparation
  1. Find the most recent backup of the Managed Metadata Service database, from your 2010 farm, and then copy it to the SQL Server host of your 2013 farm.
  2. If you already instantiated the Metadata service on your SharePoint 2013 farm, you will need to completely remove it:
    1. Navigate to: CA > Application Management > Service Applications > Manage service applications.
    2. Select the Managed Metadata Service application.
    3. On the Service Application ribbon, click the Delete button.
    4. Enable the option, Delete data associated with the Service Applications.
    5. Click OK.
    6. When completed, click OK again.
    Note that deleting the Metadata Service Application also deletes the Managed Metadata Service Connection.
Procedure
  1. In SQL Server Management Studio, perform a restore of your 2010 farm Managed Metadata Service database.
  2. After restoration, map the farm administrator and farm service accounts to the restored database both as db_owner.  Also add your own administrator account as db_owner.
  3. In Central Administration, navigate to: Application Management > Service Applications > Manage service applications.
  4. On the Service Applications ribbon, click New, and then click Managed Metadata Service.
  5. On the Create New Managed Metadata Service dialog, enter:
    1. Database Name: [enter the name of the restored database].
    2. Other fields: as appropriate to your farm.
  6. After this completes, click the name of the Managed Metadata Service listed.
  7. Verify that the appropriate taxonomy store is shown.
References
Notes
  • This procedure performed on Windows Server 2012, SQL Server 2012, SharePoint Server 2013.

1 comment:

Martin said...

Thanks, great step by step description. Works also still for migration from 2013 to 2016.