One migration tidbit to note when going from 2010 to 2013. Search scopes are contained in the Search Service database..NOT the content database. This means that if a site heavily relies on search scopes..and you are choosing to keep this site in “2010 Mode” (Not generally recommended, but sometimes makes sense) then you will need to upgrade the Search database as well. This is because sites running in “2010 Mode” will use existing scopes, but you cannot create new search scopes after the content database is upgraded to SharePoint 2013. Side Note – If this site collection is upgraded to SharePoint 2013 then you can use the fancy shmancy new result sources.
The search database can be upgraded using the following PowerShell cmdlet:
More about this cmdlet here: https://technet.microsoft.com/en-us/library/ff608131.aspx
This process is rock solid…kind of. It doesn’t give you GUIDs, but the search database names are in the following format:
- <Search Service Application Name>_AnalyticsReportingDB
- <Search Service Application Name>_CrawlDB
I had a DB naming format and this did NOT work for me. The search Admin DB (The one I restored) was renamed as I went through the SQL backup/restore process so it had the naming down. I used the process described here to get everything nice and clean: http://www.andrewjbillings.com/sharepoint-2013-foundation-creating-the-search-service-with-powershell-and-removing-those-pesky-guids/
Search database names were clean..search scopes were showing up. Life is good