SharePointSupport

SharePoint performance is a recursive problem and preoccupation. As a Database Administrator, we have to deal with SharePoint when configuring SQL Server databases. In this article, I will propose a list of best practices in SQL Server settings aimed to reduce SharePoint performance issues. Autogrowth Do not keep the default value which is 1 MB. We can illustrate with a simple example why this is a bad idea. When a document of 5 MB is uploaded, it means there are 5 Autogrowth which are activated. In fact, there are 5 allocations of space which must slow your system. Moreover, your uploaded document will be fragmented across your different data files. This configuration will decrease your performance a second time. To avoid performance issues and reduce fragmented data files, you should set the autogrowth value to a fixed number of megabytes. My recommendation is 1024 MB for data files and 256 MB for log files. But keep in mind, this is a global recommendation. In f

One of the most talked about capabilities since the launch of SharePoint 2010 is the Managed Metadata Service .  For those of you who aren’t already familiar with this service and the support it provides for modelling and deploying a rich corporate taxonomy.   For those who need get to the basics, configuration & related features for it, we would recommend going thru the links available at " Managed Metadata and Taxonomy in SharePoint Server 2010 " We would use this blog post  to bring about some additional information on situations which you might face in day to day work . The Taxonomy Field is lookup field. The taxonomy field is a lookup field. The lookup list associated with this field is called the Taxonomy Hidden List. This list is located at http://siteURL/lists/taxonomyhiddenlist . It exists only on the root web of the site collection, and is used as lookup by all the site/list taxonomy fields within that site collection. Every time a term is used

Here are five storage-related issues in SharePoint that can kill performance, with tips on how to resolve or prevent them. Problem #1: Unstructured data takeover . The primary document types stored in SharePoint are PDFs, Microsoft Word and PowerPoint files, and large Excel spreadsheets. These documents are usually well over a megabyte. SharePoint saves all file contents in SQL Server as unstructured data, otherwise known as Binary Large Objects (BLOBs). Having many BLOBs in SQL Server causes several issues. Not only do they take up lots of storage space, they also use server resources. Because a BLOB is unstructured data, any time a user accesses a file in SharePoint, the BLOB has to be reassembled before it can be delivered back to the user – taking extra processing power and time. Solution: Move BLOBs out of SQL Server and into a secondary storage location – specifically, a higher density storage array that is reasonably fast, like a file share or network att

Manage the search schema in SharePoint Server 2013 Learn how to view, add, edit, map, and delete crawled properties, crawled property categories and managed properties in the search schema. Manage the Search Center Learn about pages that are created in a Search Center site in SharePoint 2013, and see articles about how to configure Web Parts. Manage search relevance in SharePoint Server 2013 Learn how you can configure settings to provide the most relevant search results. Manage crawling in SharePoint Server 2013   Learn how to crawl content that you want users to be able to search for in SharePoint 2013. Manage the search topology in SharePoint Server 2013 Learn how to manage search components to scale out the search topology in SharePoint 2013. View search diagnostics in SharePoint Server 2013 Learn about search and usage reports, query health

When you create an Enterprise Search Center site collection as described in Create a Search Center site in SharePoint Server 2013 , SharePoint 2013 creates a default search home page and a default search results page. In addition, several pages known as search verticals are also created. Search verticals are customized for searching specific content, such as People, Conversations, and Videos, and they display search results that are filtered and formatted for a specific content type or class. The following pages are created in an Enterprise Search Center site collection: default.aspx: the home page for the Search Center, and the page where end-users enter their queries. results.aspx: the default search results page for the Search Center. It is also the search results page for the Everything search vertical. peopleresults.aspx: the search results page for the People search vertical. conversationresults.aspx: the search results page for the Conversations search vertical.

As you may remember in SharePoint 2010 you had a specific user interface to create and reconfigure your enterprise Search topology, in the Search Service applications management.  There you can create, edit and remove the following components: Admin component Crawl components Crawl databases Query components Partitions And it was very easy by the administrator to use any server in their farm to configure the best enterprise Search topology for their business requirements. One thing than many people said to me was that the configuration was very easy with the UI, but if you put something wrong or your farm have any issue, when you finished to reconfigure your enterprise search topology, and you click in the button to apply all the changes, it takes a while and gives you an error and also you lose the majority of the changes that you made before. The above problem was a good reason to configure your enterprise search topology with Power Shell, because you have t

If you, like me, are playing with SharePoint 2013 or if you have plans to migrate/deploy SharePoint 2013, you may have already heard about Distributed Cache (a.k.a. Velocity or AppFabric).  In this post, I’d like to make you aware of some tips from the field that may help you avoid some serious issues in your production Farm. First things first, see the following articles to learn about planning and managing Distributed Cache on SharePoint 2013: Plan for feeds and the Distributed Cache service in SharePoint Server 2013 Manage the Distributed Cache service in SharePoint Server 2013 As you know, real world scenarios are always different and more challenging than TechNet “ideal world” and some tips that we noted from Premier support cases are really valuable: When you run Configuration Wizard on SharePoint 2013 (a.k.a. psconfig), Distributed Cache service is enabled by default on that server.  If you run the wizard on all SharePoint servers in the Farm, the service will be run

ISSUE The Distributed Cache service does not install correctly on additional farm servers. SYMPTOMS When you join a server to the farm the Distributed Cache service on the server does not start. When you try to manually start or provision the service, you receive an error or the exception: cacheHostInfo is null When you try create a new Distributed Cache instance on a server that is not part of the Distributed Cache cluster using the  Add-SPDistributedCacheServiceInstance  cmdlet you receive the exception: ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster In both cases: The Distributed Cache service has been created and is running on one or more other servers in the farm The AppFabric ports (TCP 22233-22236) are permitted between all servers in the farm SharePoint has created a new Distributed Cache SPServiceInstance on the server, but it is Disabled The AppFabric Windows service (AppFabric Caching Service) is not running