This article will provide tips and tricks regarding SQL performance improvement.
The SharePoint server health is directly connected with the SQL server health. If your SQL server is suffering because of poor performance the impact will be reflected in your SharePoint environment. User experience will be degraded more and more if you are not acting in time.
Every time when you want to grant permission for a user or group in a SharePoint application you will use this SharePoint people-picker interface.
![clip_image002[4]](http://www.sharepointboco.com/wp-content/uploads/2012/01/clip_image00242.jpg "clip_image002[4]")
![clip_image004[4]](http://www.sharepointboco.com/wp-content/uploads/2012/01/clip_image00442.jpg "clip_image004[4]")
How does people-picker work?
When you type a keyword to find a user or a group, people-piker will first make a query on the content database and if there are no results, it will make the second LDAP query on the DC. More info in this article
SharePoint 2010 lists and libraries can hold a maximum number of 30,000,000 items. In a SharePoint site the list view threshold is 5000 for users and 20,000 for auditors and administrators.
SharePoint large list and libraries operations like Delete/Update are one of the top performance killers.
What can we do if the server is overloaded when we access large lists and libraries? One solution is list view throttling.
Two months ago I was at a SharePoint conference where I saw a nice presentation of Dan Holme regarding blob storage.
As per Microsoft definition – a binary large object (BLOB) is a large block of data stored in a database that is known by its size and location instead of by its structure — for example a Microsoft Office 2010 document or a video file.
The following article describes the steps to create a stress test using Visual Studio 2010 Ultimate
1. Start Visual Studio 2010 Ultimate
2. Click on Test and then New Test
