16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

168 Part III: Planning <strong>and</strong> Deployment<br />

The method used to update the index can have a significant effect on performance.<br />

The following topics describe these four methods.<br />

Full Update<br />

During a full update, SharePoint Portal Server updates all content in a content index. A<br />

full update of a content source includes adding new content, modifying changed content,<br />

refreshing the content index for existing unchanged content, <strong>and</strong> removing<br />

deleted content from the content index. This is the most time-consuming <strong>and</strong> resourceintensive<br />

type of update, <strong>and</strong> it should be done only in the following situations:<br />

■ If you create a new rule that affects only one content source.<br />

■ If files are renamed in a specific content source.<br />

■ If it is the first crawl of a content source.<br />

■ If you include or exclude a new file type.<br />

■ If permissions are changed on documents in the content source. While all<br />

updates pick up permission changes, only the full updates pick up changes to<br />

membership in local groups. This is why it is recommended that you not use<br />

local groups to secure content that SharePoint Portal Server crawls.<br />

■ If there is a power outage. In this case, SharePoint will want to run full<br />

indexes to reset the index. It might be faster to reset the index files <strong>and</strong> clean<br />

them out before running a full index. (Resetting the index files is discussed in<br />

Chapter 22.)<br />

■ If you change the noise word file.<br />

■ If there is an area name change.<br />

■ If you reset the content index.<br />

Given all these changes that will force you to rerun a full index, it is best that<br />

you plan for them so that the full indexes can be run without overloading either the<br />

indexing server or the content source’s server.<br />

Incremental Update<br />

An incremental update of a content source includes only changed content. Share-<br />

Point Portal Server does not remove deleted content from the content index <strong>and</strong><br />

does not recrawl unchanged content. For this reason, performing an incremental<br />

update is faster than performing a full update.<br />

You can perform an incremental update if you know that content has changed<br />

but you do not want to perform a full update <strong>and</strong> you don’t mind having some<br />

deleted content continue to appear in your index. A periodic incremental update<br />

creates the index without using the time or resources required for a full update,<br />

which enables you to perform a full update less frequently.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!