Full-Text Index

(2) Share

Report

Posted on by Community Member

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

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Daniel at VNS on at

Like (0)

Report

Hi Jason. if you mean the global quick find, it sounds like you may not have the desired fields in your quick find view filter criteria. the global quick find just leverages the existing quick find views for every entity so that might explain why you aren't seeing it via QF but you can find the data using advanced find.

also, the global QF will return first 3 fields you have in your quick find view, and display up to 80 records.

Was this reply helpful? Yes No
tpeschat 4,930 on at

Like (0)

Report

Do you have any maintenance jobs for your CRM indexes running and are they finishing?

You may want to read through: blog.westmonroepartners.com/5-ways-to-improve-microsoft-dynamics-crm-performance

br Thomas

Was this reply helpful? Yes No
Daniel at VNS on at

Like (1)

Report

fyi - crm job editor (referenced in article) does not run on 2016. that blog was also written for 2011 and i don't know that i'd implement everything in there until it's updated for 2016, since there have been so many changes since 2011.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

It sounds as though your indexes are not being updated. These normally get updated by the Indexing Maintenance job every 24 hours. However if there are problems with an index, the sp that rebuilds the index will bomb out with an exception. You can test this by running p_Reindex and seeing if you get any error messages printed. Since I have had a scenario where I have a missing index that I have not been able to fix by the conventional method of deleting and recreating in settings, I have copied the p_Reindex function and wrapped the DBCC calls in try...catch blocks and I now run this in a SQL maintenance plan. I don't understand why p_Reindex was not implemented in this way in any case.

HTH

Was this reply helpful? Yes No