Hello,
I was wondering if anyone has some details in regards to maintaining the quick search - full text index from the SQL side? I've encountered an issue where there are records that are not indexed and as a result are not coming up as matches in quick search. I've found that rebuilding the full-text catalog has resolved this in the non-prod environments. I suspect the issue we are experiencing in prod stems from a backup/restore that had been done during an upgrade from CRM 2013 to 2016. Few questions:
- Are there any documents covering maintenance of the full text catalog/indexes from a CRM perspective? I've yet to find any
- Has anyone experienced any issues post upgrade with search issues where some records aren't found via quick search, but can be via advanced find? In this scenario I've found that modifying the records not found causes them to subsequently be found - This is due to change tracking for Full Text search
Any pointers would be greatly appreciated!
Thanks!
Jason Neuman