Sharepoint Insight by Namwar Rizvi

Sharepoint Tips, Tricks and inside knowledge from real world experience by Namwar Rizvi

Archive for the ‘Architecture’ Category

How to solve never ending “Sleeping for 10 seconds” upgrade message of SharePoint

Posted by namwar on June 13, 2010


While performing upgrade, sometime SharePoint got stuck and continously log message “Sleeping for 10 seconds…” in Upgrade.Log . To solve this issue, just perform following two steps

  1. End the task psconfig.exe,if it is running,  from task manager.
  2. From command prompt, execute the following command psconfig -cmd upgrade -inplace b2b -wait -force
  3. Wait to complete the upgrade. Once done, just browse your SharePoint site as usual, it will be back again:)

Posted in Architecture, Solutions, Troubleshooting | Tagged: , , | Leave a Comment »

Displaying only Year in SharePoint Calculated Column

Posted by namwar on November 26, 2009


I wanted to display just the year of a DateTime column of SharePoint. I created a calculated column and set the formula to Year([MyDateTimeColumn]). The result I got was 2,009 ; 2,008 etc. which offcourse incorrect for year. After searching through internet, I found a good article solved my problem.

The correct formula is TEXT(YEAR([MyDateTimeColumn]),”000″)


Posted in Architecture, Customization, Solutions, Tips | Tagged: , , , | Leave a Comment »

List of all SharePoint Back-End databases

Posted by namwar on July 16, 2009


SharePoint stores end-user content and application configurations across multiple relational databases in the back-end database servers. At a high level, the following are the relational databases:
 Configuration database: Stores topology and configuration information for the complete deployment. Every farm has exactly one configuration database. For information about the configuration database protocols, see Configuration Database.
 Central Administration content database: Stores content associated with the Central Administration site.
 Shared Services Providers (SSP) database: Stores content and configuration for Shared Service Providers (SSPs), such as the user profile services. The capabilities of SSPs are described in [MS-SPFEPO], Section 2.2.2 (Shared Service Provider).
 Shared services administration content database: Stores content for the shared services administration site.
 Content database: Stores all end-user and site content. For information about content databases and protocols, see List and Library Storage.
 Search property store: The search metadata index that stores properties related to pieces of content that are indexed for full-text querying. For information, see section 7.4.1.1.2.
11 of 43
[MS-SPBEPO] SharePoint Back-End Protocols Overview – v1.0
[MS-SPBEPO]: SharePoint Back-End Protocols Overview
Copyright © 2008 Microsoft Corporation.
Release: Friday, June 27, 2008
 Single sign-on database: Stores credentials for end-users to access information from external applications through SharePoint. For information about the protocols used to access the single sign-on (SSO) database, see Business Data Catalog Protocols.

As described by Microsoft in SharePoint Back-End Protocols Overview

SharePoint stores end-user content and application configurations across multiple relational databases in the back-end database servers. At a high level, the following are the relational databases:

  1. Configuration database: Stores topology and configuration information for the complete deployment. Every farm has exactly one configuration database.
  2. Central Administration content database: Stores content associated with the Central Administration site.
  3. Shared Services Providers (SSP) database: Stores content and configuration for Shared Service Providers (SSPs), such as the user profile services.
  4. Shared services administration content database: Stores content for the shared services administration site.
  5. Content database: Stores all end-user and site content.
  6. Search property store: The search metadata index that stores properties related to pieces of content that are indexed for full-text querying.
  7. Single sign-on database: Stores credentials for end-users to access information from external applications through SharePoint.

Posted in Architecture, Debugging, Guidance, Management, Tips | Tagged: , , , , , | Leave a Comment »

How Sharepoint ranks a document in Search Results?

Posted by namwar on January 12, 2009


Several times I have been asked about the way Sharepoint calculates the rank of a document in document search. Although, it is based on a complex probablistic algorithm developed by Microsft Researcher, following are some simple tips to know the background of search ranking and how to tune the search results. Please note, these tips are not an authentic statements from Microsoft, instead they are my observations and knowledge gained from other fellow Sharepoint experts.

According to Microsoft on Technet in this article

Ranking depends on:

  • The length of the document
  • The frequency of the query term in the entire collection of documents
  • The number of documents containing the query term
  • The number of documents in the entire collection of documents
     

Keeping the above points in mind, following observations have been made as mentioned in this blog

  • Higher size of the document = lower ranking
  • More frequent the keyword matched in a document = higher ranking
  • Deeper URL surf depth = lower ranking
  • Authoritative pages in SP = higher ranking
  • Default views seem to get ranked higher than individual item views
  • File types seem to affect ranking (.doc > .txt for instance)
  • Language seems to affect ranking, US-EN is always higher, even though your server installation may have french as it’s default language

Posted in Architecture, SSP | Tagged: , , , | Leave a Comment »

List of SharePoint URL tokens

Posted by namwar on December 1, 2008


Following is a list of tokens available in Sharepoint to use in your URLs. Be aware that Sharepoint only replaces the value of a token once for a given string, so if you have used the same token twice, second occurance will not be replaced by the token value. I will post a solution to do it in my next article:

~site – Web site (SPWeb) relative link.

~sitecollection – site collection (SPSite) relative link.

In addition, you can use the following tokens within a URL:

{ItemId} – Integer ID that represents the item within a list.

{ItemUrl} – URL of the item being acted upon. Only work for documents in libraries. [Not functional in Beta 2]

{ListId} – GUID that represents the list.

{SiteUrl} – URL of the Web site (SPWeb).

{RecurrenceId} – Recurrence index. This token is not supported for use in the context menus of list items.

Posted in Architecture, Customization | Tagged: , | 4 Comments »

How to crawl Lookup field or column

Posted by namwar on October 5, 2008


Whenever you create a column in your list and want to enable search based on it then you add that column as a Managed Propety in your Shared Service Provider. It works for all type of columns except lookup columns, which actually refers to another list in the site, without needing any further steps. The difference in lookup columns is that they actually save just a reference not the actual value and if you have created a column with the name say Category ( having values Hardware, Software, etc) and add it as a managed property then you will see that you will not get any result if you will try to search by say Hardware,a value from the Category list, because internally only reference was saved and SSP indexed the reference not the actual value.

But don’t worry, there is a simple solution which unfortunately Microsoft has not documented properly. The solution is, just go back and edit your managed property mapping and instead of mapping Category; map ows_Category. This is an internal property generated by the Sharepoint when you created Category and this property saves the actual value.

Now, after doing the crawl, if you will search as before, you will get the expected result.

Posted in Architecture, SSP | Tagged: , , | Leave a Comment »

Sharepoint best practices: how many sites, how many libraries

Posted by namwar on August 26, 2008


While browsing Sharepoint newsgroups, I found a very useful reply from Eddy Blanco which provides excellent information to estimate your SharePoint site and structure. Following is the information, all credit goes to Eddy Blanco:

SharePoint Area of Interest Optimum Size
Site collection 50,000 per Web application
Web site 250,000 per site collection
Subsite 2,000 per Web site
Document 5 million per library
Item 2,000 per view
Document file size 50MB (2GB max*)
List 2,000 per Web site
Field type 256 per list
Column 2,000 per document library 4,096 per list
Web Part 50 per page
Users in groups 2 million per Web site
User profile 5 million per farm
Security principal 2,000 per Web site
Search indexes One per SSP, Maximum of 20 per farm
Indexed documents 50,000,000 per content index
Content sources 500 per SSP
Start Addresses 500 per content source
Alerts 1,000,000 per SSP
Scopes 200 per site
Display groups 25 per site
Crawl rules 10,000 per SSP
Keywords 15,000 per site
Crawled properties 500,000 per SSP
Managed properties 100,000 per SSP
Authoritative pages 200 per relevance level
Results removal 100
Crawl logs 50,000,000
Shared Services Provider (SSP) 3 per farm (20 per farm maximum)
Zone 5 per farm
Web application 99 per SSP
Internet Information Services (IIS) application pool 8 per Web server
Site collection 50,000 per Web application
Content database 100 per Web application
Site collection 50,000 per database
Index servers 1 per SSP*
Application servers running Excel Calculation Services No limit
Query servers No limit
Web server/database server ratio 8 Web servers per database server
Web server/domain controller ratio 3 Web servers per domain

Posted in Architecture | Tagged: | Leave a Comment »