Migration from 2012R2 to 2016 -Portal "content"
I am testing moving from 2012R2 to a 2016 farm. The LifeCycle app was able to do most of the lifting for the console but in my environment we have spent a lot of time with dashboards and the navigation looking if anyone has run thru a process like the KB for moving KB content.
Best Answer
-
john_doyle Cireson Support Ninja IT Monkey ✭✭✭✭Hi Brian,
Why don't you just take the existing ServiceManagement database, copy it and then install the new portal against this database? You can run the usual commands from a full resynch if you need to clear old data.
5
Answers
Why don't you just take the existing ServiceManagement database, copy it and then install the new portal against this database? You can run the usual commands from a full resynch if you need to clear old data.
And what should one do if the portal has already been installed using a new database?
Can I just delete and replace the old database?
Deleted the current ServiceMangement DB installed from the 2016 installer
Stopped the cache builder
Deleted the DB
Lift and dropped the Old DB
Truncated tables that the cache builder builds
Ran the installer again to make sure the connection strings were in place
Allow the cache builder to repopulate the truncated tables.
This provided us a full replica of the production instance.
Brian,
Last question, using which commands did you truncate which tables?
Thanks!