Ting Li talks about Azure, SharePoint and .NET

A team member asked me why in some situation we need to use SharePoint search on local file drive as we can do 'search' directly on the folder in windows. I think it is necessary to do some research to show why and why the benifit is to do this. And more importantly - HOW.   WHY? If you've played around with SharePoint local file search the answer is straight-forward: You can let it search multiple local file drives, but using windows you can hardly do this. SharePoint can search 'into' the real content even the keyword is in content of files in zip file . See the comparison I did a search for keyword 'issue':   Window built-in search: SharePoint search: SharePoint search can easily filter the result by type/date etc. SharePoint can show a bit of content from the files found to give a bit more indication. ... HOW  It's hard to find a step-by-step guide talking about how to make it work. That's why here I am:-)   Go to the f...

From time to time when you do some operations such as search using SharePoint 2013 you may see the following error: Unexpected response from server. The status code of response is ’500′. The status text of response is ‘System.ServiceModel.ServiceActivationException’ After having this issue on newly installed SharePoint 2013 farm in production environment, I figure it out that Single server is running out of memory. Especially, thanks to one new process noderunner.exe. Noderunner.exe is the new executable of search service on SharePoint 2013. This process can’t turn it off because Search is one of essential service application in SharePoint 2013, and it is integrated in many features. So, there are some things you can do to reduce the impact of Search on your system. Solution 1 Reduce the Search Service Performance Level with this PowerShell command: Set-SPEnterpriseSearchService -PerformanceLevel Reduced or Set-SPEnterpriseSearchService -PerformanceLevel PartiallyReduced,...