Showing posts from January, 2014

SharePoint 2013 Search Farm Installation Architecture Matrix

General Guideline: SharePoint 2013 Search Farm installation general guideline. So how would be the search farm structure? To installation each component in farm that you need to analysis the number of item in your organization. So if the content less < 10 mil then 2 index component and 1 partitioned per 10 mil items,  2 Query, 2 content processing, 2 Analytic, 1 crawl database and 1 link database. 
For the performance issues:
Crawl time and result freshness: Add crawl database and content processing component for improve the crawl time and result freshness.Result time: For query latency add more index replica and for query throughput add more partition
Use the following matrix to configure Search Farm

Use 2 Crawl Component Use 2 Search Administrator ComponentNumber of Analytic database varies depend upon the usage

Issue Solved: Missing Fast Search Center Template

Today we encounter an issue related to the "Fast Search" missing template.

When we creating the site collection by going into the central admin and select the "Fast Search" template the default the "Fast Search Template" feature activated and this template is available for all the sub sites as well. The problem comes when we creating the site collection other than this template like "teamsite" template. The "Fast Search Template" feature is deactivated by default. So
we unable to find the search template under this site collection, for that we would req. to activate this feature manually.

So we need to run the following Power shell.

$site = Get-SPSite -Identity http://Sp2010/sites/Search

Issue Solved: WSP Deployment Showing Deploying Status

This issue comes when we are deploying WSP solution to our SharePoint Farm. When we activated the solution timer job created with future time. We waited for the timer job to complete but nothing happen still showing deploying.

In our farm we have 4 WFE servers we have check many blogs related to this type of issue like mentioned below.
We check the all WFE servers and found the most of the servers following two services was stopped.  SharePoint Timer serviceSharePoint Administration  

So I stated both two services in all my WFE servers and the problem solved.

SharePoint 2013 Search Bound Variables

SharePoint 2013 search architecture almost changed and the new word that I heard today is "Search Bound Variable”. So I deep dive into it.
So the “Search Bound Variable” that you find most of the places during the search configuration & you also wanted to know they it is working and interaction during the query processing.

Search bound variables: The search bound variables are the place holders. So the most common search bound variables are following.

As showing below image in comes the search "cameras images" the {searchboxquery} text is "cameras images". When the query transforms the {searchboxquery} breaks in {subjectTerms} and the "{actionTerms}" to the below example during the query rules the "cameras" is treated like the {subjectTerms} and "images" become {actionTerms}.

As the per the above example in search term "Cameras Images" to explain below how bound variables works.
{searchboxquery} : Whatever in the sear…

SharePoint 2013 Search Extensibility Points

SharePoint 2013 buzz word "Search 2013 Extensibility" related to the Search prospective. In SharePoint 2013 following are the points where we can customize the search experience.  BCS Connector Content enrichment web service Custom entity extraction Pre/post security trimming Custom Ranking ModelsUser Experience (UX)
BCS Connector: SharePoint 2013 there are some of the new method added in the BCS entity connector framework that works well and more stable for large items. Crawl data from the external system you can use the BCS connector and crawl the data into your SharePoint 2013. Please refer the below link that refer the BDC Mode properties and method that need to incorporate in your BDC file.  SharePoint BCS Connector and its method that required for crawlNo CodeODataSQLCode.Net AssemblyWCFBCS Request Methods  Full CrawlFinder(): Return All DocuemntSpecificFiner(Id1): Return the properties to the single Item. StreamAccessor(Id1) (Optional): Only way to get the data like a…

SharePoint 2013 Search Database Part 2 (Link Database & Analytic Database)

Link Database:  This database store analyzes content that is being crawled and added to the search index. The usage information means the user actions or usage events, such as click or viewed items on a SharePoint Site. Link database Stores information extracted by the content processing component and search click information. Store the information based on the click also store the search reports.

1.MSSConfiguration 2.MSSOrdinal 3.MSSQLogO14PageClick 4.MSSQLogPageClick : Query suggestions are automatically generated for a query when users click a result for that same query at least 6 times. Users’ clicks on results are logged and entry pairs of (query, result) are added to the Analytics Link Store DB, specifically to the MSSQLogPageClick table. 5.MSSQLogPageImpressionBlock 6.MSSQLogPageImpressionQuery 7.MSSQLogPageImpressionQueryRule 8.MSSQLogPageImpressionResult 9.MSSQLogPageImpressionResultTemp 10.MSSQLogPageImpressionResultUnprocessed 11.MSSQLogResultDocs 12.MSSQLogResultDocsTemp 1…

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use.

Following are the List of DB (FS4SP)
FASTContentSSASearch Service Application DBSearch Service Application Crawl Store DBSearch Service Application Property Store DBFASTQuerySSASearch Service Application DBSearch Service Application Crawl Store DBSearch Service Application Property Store DBFASTSearchAdminDatabase: Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experienced improve.

Following are the l…