Here is the common scenario:

General task: upgrade old SP2013 environment to SP2016.

Service applications that need to be migrated:

  • Managed Metadata
  • Subscription Services
  • Excel services
  • SSS
  • etc

Approach we used: We've just created new Service Applications that would point to the migrated databases. Like so:

$mms = New-SPMetadataServiceApplication -Name 'Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'Managed Metadata Service OLD SP 2013 DB'
New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service Application Proxy" -ServiceApplication $mms -DefaultProxyGroup

Long story short, all went well. The databases were upgraded. The Client tested the new environment and now we are ready for the cutover. During the testing period the old environment was actively used and now I need to migrate the databases one more time. Do a data refresh for all service applications

The question is: What is the best way to refresh the databases one more time? Do I delete all service applications and run the New-***ServiceApplication command one more time? or there is an easier "refresh" method?

Recreating the databases is not a hard task. I can do it, but I've been thinking if there is a "refresh/upgrade" method that I'm missing.

1 Answer 1


The way to migrate is to delete all of the Service Applications and then create new ones off of the newly restored databases.

  • Oh well, I'll do it this way then Commented Aug 15, 2017 at 17:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.