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.

Planning Alerts<br />

Chapter 8: Planning Your Information Structure 169<br />

Incremental (Inclusive)<br />

SharePoint Portal Server 2003 introduces another type of update known as the incremental<br />

(inclusive) update. This update is similar to the incremental update except<br />

that it includes deleted content. The incremental (inclusive) update also detects<br />

deleted entries in the <strong>Microsoft</strong> Windows SharePoint Services document libraries <strong>and</strong><br />

lists. The incremental update detects modified or new documents <strong>and</strong> list items only.<br />

The incremental update is the least expensive update if it is used with Windows<br />

SharePoint Services sites. The incremental (inclusive) update is more resource<br />

intensive than the regular incremental update <strong>and</strong> should therefore be run less often<br />

if performance is a top priority for you.<br />

Adaptive Update<br />

An adaptive update, like the incremental update, crawls only the content that, statistically<br />

speaking, is most likely to have changed since the last adaptive update.<br />

Because adaptive updates are likely to miss at least some content changes, these<br />

updates will crawl all the content in a content source every two weeks.<br />

Unlike the incremental update, the adaptive update increases its efficiency<br />

every time it is run based on a statistical analysis of the historical information on what<br />

content has <strong>and</strong> has not changed. The time required for an adaptive update varies<br />

<strong>and</strong> is based on the different types of content sources <strong>and</strong> the protocol h<strong>and</strong>ler.<br />

The recommended approach is to run adaptive updates daily for large source<br />

groups <strong>and</strong> more often for smaller source groups. Avoid running full updates whenever<br />

possible. However, how you choose to configure your index updates is dependent<br />

on your search requirements. If your organization is search intensive <strong>and</strong><br />

requires immediate updates to the search indexes as new content is added or<br />

removed, you might need to schedule updates to occur more frequently. You must<br />

balance the search requirements with the time it takes to perform an update <strong>and</strong><br />

propagate content indexes.<br />

There is also a scheduling factor to consider too. Updates are both processor<br />

<strong>and</strong> RAM intensive. You’ll want to ensure that you’re scheduling your updates to<br />

occur when your servers running SharePoint Portal Server <strong>and</strong> Windows SharePoint<br />

Services are not being backed up, scanned for viruses, or performing any other routine<br />

that consumes large processor resources, RAM resources, or both. In addition,<br />

you shouldn’t crawl content sources during their nightly routines either. Therefore,<br />

a best practice is to create a schedule matrix <strong>and</strong> schedule the crawling of content<br />

sources when those sources are being used the least.<br />

Alerts provide notification when information of interest is added or updated on the<br />

portal site <strong>and</strong> associated content sources. You can define areas of interest <strong>and</strong> identify<br />

how <strong>and</strong> when you want to be notified. You can add an alert to track new

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

Saved successfully!

Ooh no, something went wrong!