Hot answers tagged indexed-column
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)
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 ...
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. ...
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.
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 ...
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