Bolufer Blog - SharePoint & .NET language

SQL Aliases  are optional ( but recommended ), and are a great way to configure your SharePoint environment. They allow for flexibility in case the SQL instance is changed, or the server names/IPs change then it’s possible to only “ re-point ” to the new servers. This way, there’s no need to reinstall SharePoint for the new server/instance. SQL Aliases are  configured on each SharePoint Server . This is very important to remember! Let’s dive in and configure our aliases. Run  cliconfg  utility on SharePoint Server On Windows Server 2012 R2 & Windows Server 2016, we have an utility called  cliconfg . There are 2 versions:  32-bit and 64-bit. In this blog post, we will be installing the  64-bit version  ( 32-bit would be for apps compatibility, and located at C:\Windows\SysWow64 ) Log into the SharePoint Server Browse to  C :\Windows\System32 Double-click on  cliconfg cliconfg utility location When the...

Step 1: Reduce the CPU impact of the search service By default SharePoint search uses "maximum" to speed up its search crawling process. To reduce the CPU usage of the search service, run this PowerShell script from any one of your SharePoint 2013 server: 1 Set -SPEnterpriseSearchService -PerformanceLevel Reduced     setting it to reduced is the correct way go about it: on dev machine: Set-SPEnterpriseSearchService -PerformanceLevel Reduced restart sharepoint search service on production if hardware is tight than use PartlyReduced Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced restart sharepoint search service on a live server where the search service is over serveral servers within a farm with 4 cores each with atleast 8gb ram: leave it as it is: Set-SPEnterpriseSearchService -PerformanceLevel Maximum restart sharepoint search service   This sets Search Service Application crawl component to use less number of th...