Tag Info

Hot answers tagged

6

The problem i've encountered was linked to the reference i was using.. I used Microsoft.SharePoint.Search.Query instead of Microsoft.Office.Server.Search.Query In the version i was using it was impossibile to query sharepoint giving him parameters and so on... But the firm of every class and method was the same.. Now it works! Thanks to all!


5

Try using a KeywordQuery and setting the RankingModeID to "D9BFB1A1-9036-4627-83B2-BBD9983AC8A1" This PowerShell code works for me Add-PSSnapin Microsoft.SharePoint.PowerShell $site = get-spsite "http://localhost" $kq = new-object Microsoft.Office.Server.Search.Query.KeywordQuery($site) $kq.ResultTypes= ...


4

This is a pretty big question so I'll do my best to outline the steps you'll need to take in order to get this done. First, you'll want to make sure all of your columns are crawled. If you're using out of the box Tasks lists then some of them may already be in there. If not, it will take some monkeying around in Central Admin (full disclosure: link to my ...


4

Try using the KeywordQuery class instead, that should mimic the search box behaviour as far as I'm aware.


4

Download Fast Search Tool from Codeplex, use UI to construct the query, and test. Repeat until you get it working. (I have nothing to do with the tool, I have just used it for similar purposes)


3

I'm guessing that Tag is a Managed metadata column? If so, doing an equals compare using Column = 'Value' won't work, as the actual text in the property could potentially hold more values, lookup value based managed metadata properties store the values differently in the index. So you would have to use a CONTAINS or a LIKE. Any search using a lookup column ...


3

You didn't mention it in your question so just to make sure... Did you perform a Full Crawl of the content source AFTER you mapped the ows_DueDate crawled property to the TaskDueDate managed property? Do you know for sure there is content with a value for the ows_DueDate crawled property? SOLUTION: The problem was due to teh fact that the ...


2

Theres lots of info out there on what columns you can use http://msdn.microsoft.com/en-us/library/ms495418(v=office.12).aspx http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/03/06/how-to-use-the-moss-enterprise-search-fulltextsqlquery-class.aspx Regarding using * wildcard in query syntax see my answer here: ...


2

Permissions aren't indexed in search (there's no reason to do so, either), so the only way to get the permissions mask is exactly what you said in your question.


2

You can add something like this to your query: AND site = 'http://blah/subsite/anothersite' But in general I'd recommend that you move to KeywordQuery syntax instead of FullTextSqlQuery as the later isn't supported by FAST.


2

Do you have a managed property called mypublishstartdate which has a crawlable property mapped to it?


2

Have you set the "Reduce storage requirements for text properties by using a hash for comparison" option for your FooText managed property?


2

AFAIK you have to specifically mention the columns you want. In the SQL query, you are allowed to use the asterisk (*) to specify that all columns in a table are to be returned. However, no defined and fixed set of properties applies to all documents. For this reason, the SQL asterisk is not permitted in the [columns] setting. ...


2

Out of the box content type property doesn't work in queries. So workaround to this problem is to create new managed property and map this new managed property with crawled properties with which ContentType managed property is mapped (see below). See link for more details


2

Don't access the data directly in the SharePoint database. The database structure is difficult to workout and also Microsoft will not support your SharePoint environment if you are reading data straight out the database! As TZHX says use the Web Services or even better use the REST interface or the Client Side Object Model instead. They have been built for ...


1

We get the same issue, and the only way to index a metadata column was to create a fake document and run a crawl on it to be able to use it. According to the dev team of my company, it was the only way we find to solve this. Sorry.


1

If you're querying multiple Site Collections use FullTextSQLQuery since it searches across the farm and if you plan to query Pages Library of a single Site Collection, use SPSiteDataQuery instead. I think you might need SPSiteDataQuery? SPSiteDataQuery queryObj = new SPSiteDataQuery(); //query Pages libraries queryObj.Lists = "<Lists ...


1

The FREETEXT part of the documentation mentions that escaping is done with '' but also claims it's not needed for CONTAINS ?!? When performing queries with contractions and using the FREETEXT predicate, you must escape the quotation mark in the contraction; you do not have to do this when using the CONTAINS predicate. For example, the following ...


1

The SiteContext property is not related to the scope of the query. It just specifies the alternate access mapping zone for the result urls. Otherwise, the results will always return urls for the default zone. You can set it as follows: fullTextSqlQuery.SiteContext = new Uri(SPContext.Current.Site.Url);


1

Try to use FREETEXT predicate in FullTextSqlQuery.FREETEXT matches the meanings of phrases against fields.


1

Something else in your query is causing the exception. As the checkbox description itself states, it only applies to text properties. Also, enabling this checkbox wouldn't allow you to order by in any case. According to this TechNet article (emphasis mine): In the "Optimize managed property storage section", select the "Reduce storage requirements for ...


1

How does the duplicate document is identified when we do a search? Document similarity for purposes of identifying duplicates is based only on a hash of the content of the document. No File properties (e.g. file name, type, author, create and modify dates) are input to this hash. The MSSDuplicateHashes table in the SSP’s search database holds, for each ...


1

FullTextSqlQuery uses a SQL-like syntax, but is not actually SQL. The query statement is parsed internally by SharePoint and used to query the flat index files generated by the crawler on the file system, as well as to generate real SQL queries which may be executed on the search database. You therefore cannot use '*', and are limited to specifying only ...



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