Tampa Bay SharePoint User Group
  • Blog
  • Join
    • Meeting Invite – 10/2018
  • Resources
    • SharePoint 2013 Databases
    • Default Permissions
    • SharePoint Pals (same as clicking resources)
  • Disclaimer
  • Meetings
  • Sponsors
  • About Us
  • Books
    • Building a SharePoint 2016 Home Lab
    • Troubleshooting SharePoint
  • YouTube
    • Creating a Domain Controller and Domain
    • Create Certificate Authority
    • Keypass and RDP shortcuts
    • Creating the SQL Server
    • Creating the SP Farm with AutoSPInstaller
    • Joining WFE using AutoSPInstaller
    • Create HNSC’s with Powershell and Move ULS logging
  • Troubleshooting SharePoint
  • TK
    • 2016 Builds
    • 2013 Builds
    • 2010 Builds
19 Mar 2018

Migrating a Managed MetaData database

by Stacy Simpkins | posted in: Managed Metadata, PowerShell, Server Administration | 0

To move the managed metadata database, take a copy only backup of it from your SQL server and then restore from files in your new SQL server.  I’ll write a future post on that and put a link to it here.

At this point, you already have a managed metadata service application in your target farm and you need to get it’s globally unique identifier (GUID).  Run the following:

 

1
Get-SPServiceApplication | ?{$_.name -like "*meta*"} | ft id

 

You could put that ID in a variable, or you could type it into your next set of commands that attach the new db to the Managed Metadata service application

 

Set_MMS_DB
1
2
3
4
$ServiceID = Get-SPServiceApplication | ?{$_.name -like "*meta*"} | ft id
 
$mms = Get-SPServiceApplication -Identity $ServiceID
Set-SPMetadataServiceApplication -Identity $mms -DatabaseName "MetaData"

The key to this working is that the correct DatabaseName is used.  So if your new db is named MetaDataDB, then the above script would need to be modified a little for the -DatabsaseName parameter.

The managed metadata navigation should now be working.  If it’s not, just go to manage service applications, change the managed metadata database to a database that does not exist, click OK, then change it back.  This process causes SharePoint to execute a timer job that syncs the service application up to the database.

Hope this helps someone.

Managed Metadata

Visitor statistics

  • 24525Total visitors:
  • 5Visitors today:
  • 47Visitors yesterday:
  • 253Visitors last week:

© 2016 Tampa Bay SharePoint User Group