Tag Info

Hot answers tagged

4

You can manually start a crawl by going to Shared Services - > search settings -> Content sources and crawl schedules Start full Crawl or Start Incremental Crawl Take a look at this technet article too : Crawl content (Office SharePoint Server 2007)


3

If I understand correctly you can retrieve field form filed collection of a list and set Indexed property to true $spField = $spList.Fields["FieldName"] $spField.Indexed = $true $spField.Update()


2

I've just been looking around this to see if I could help and came across this article from Microsoft: http://msdn.microsoft.com/en-us/library/ee558807.aspx. It seems to indicate that only under certain conditions are indexed columns used to your advantage. Admittedly this is a slightly different scenario from what you've described (it uses the ...


2

I have been experiencing the same issue. I believe it is because the index is not created. This is because the creation of the index itself violates the list view threshold. This is explained here: Operations, such as creating an index on a list that is over this limit, are prevented because the operation affects more than 5,000 items. ...


2

If your data source is within a site collection, use a Content Query Web Part and filter on the Task content type, or otherwise use SPSiteDataQuery. If it's split across site collections, you can only use search, and the indexing can only occur on a content source, as Anita mentioned.


2

It isn't possible to update the searchindex for just one item. An incremental crawl is necessary to update the index. Maybe it's possible to build the webpart not using the searchindex?


1

Have you set the User Profile Property to "Indexed"? Have you set the Managed Property to Searchable? I haven't tested it, but the data type MAY matter. Are you using Text, Integer or Decimal? Once you get it working you may want to look at using the "Complete Matching" flag on the property, unless you want parial matches to work as well. Also, If you ...


1

I use the following function to add an index Function AddIndex () { Param ($list,$InternalFldName) try { Write-Host "Updating index for list: $list"; $fldToIndex =$list.Fields.GetFieldByInternalName($InternalFldName); try { ...


1

As you probably are aware use of Indexing is meant to increase performance, particularly in querying, filtering and sorting in large lists, avoiding database scanning, etc. But also over-doing could fall in other extreme (beyond the actual limit of 20), e.g. remember that each update in the structure would require adding a row in NameValuePair table in ...


1

NO, Index the columns that you search and filter on, try and stay at a maximum of 2. This works exactly like a database, the more indexes the slower updates and additions become. Columns that you might want to index are: Any column that appears in JOINS or WHERE statements.


1

You can disable the limit for the administrator, or for a certain time frame to create the index. It most likely is that the number of items created happened so quickly that by the time the indexer was ready to run, it was more than 5000 items so it couldn't run. In a normal case where under 5000 items are created in a day, the indexer will have no problem ...


1

I solved a similar problem by switching my CAML comparison value type query against the WorkflowInstanceID from Type="Text" to Type="Guid". Perhaps you could change your value type to Integer like so: q.Query = "<Where><Eq><FieldRef Name='DefectID' /><Value Type='Integer'>" + DefectID + "</Value></Eq></Where>"; ...



Only top voted, non community-wiki answers of a minimum length are eligible