What are the issues in using Full Text Indexing?
Reply 1)
When we deploy full-text indexing, we select an individual public folder or mailbox store to be indexed & then conduct full-text searches on the messages and attachments contained in the public folder or mailbox store. By default, the index contains the subject and body of a message, along with names of the sender and recipient and any names that appear in the Cc and Bcc fields. The index also includes text from the following types of attachments: .doc, .xls, .ppt, .html, .htm, .asp, .txt, and .eml (embedded Multipurpose Internet Mail Extensions (MIME) messages) files.
Issues in using full test indexing :
Binary attachments, such as pictures and sounds, are not indexed.
Search results are only as accurate as the last time the index was updated. Because the content of public folders or mailbox stores changes, the index must be updated to reflect the new content.
Reply 2)
Few more issues in using Full Text Indexing are listed below:
1) Index data generated for Full Text Indexing can eat upto 10 – 40% of the store size
2) Indexing is a CPU intensive process and CPU utilization can reach upto 90% during an index refresh
When we deploy full-text indexing, we select an individual public folder or mailbox store to be indexed & then conduct full-text searches on the messages and attachments contained in the public folder or mailbox store. By default, the index contains the subject and body of a message, along with names of the sender and recipient and any names that appear in the Cc and Bcc fields. The index also includes text from the following types of attachments: .doc, .xls, .ppt, .html, .htm, .asp, .txt, and .eml (embedded Multipurpose Internet Mail Extensions (MIME) messages) files.
Issues in using full test indexing :
Binary attachments, such as pictures and sounds, are not indexed.
Search results are only as accurate as the last time the index was updated. Because the content of public folders or mailbox stores changes, the index must be updated to reflect the new content.
Reply 2)
Few more issues in using Full Text Indexing are listed below:
1) Index data generated for Full Text Indexing can eat upto 10 – 40% of the store size
2) Indexing is a CPU intensive process and CPU utilization can reach upto 90% during an index refresh
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home