In line with Microsoft's recommendation to keep content databases on SharePoint 2007 under 100Gb, we often move site collections to different content databases to balance the load. However, we have noticed a problem - after we move the site collection to a new content database, the entries in the search index for everything in the site collection disappear.
This seems strange as the paths are all maintained exactly as they were before so they should all still searchable in the exact same way. Alternatively, if the crawler wants to kick out these entries it should re-create entries for the "new" data that was relocated to another content database.
This is a big problem for us as part of our system architecture is to "archive" finished site collections to archive content databases on bigger, slower hard drives so the content is still on-line and searchable, just not on the super-fast disks that the live content is on.
Is there any way to stop this happening or to force the site to be re-crawled in its new content database? We don't want to do a full crawl as the last one we did took more than eight days and in any case we would still have the same problem after the full crawl when we next move site collections.