Community Kit for SharePoint 2.0 Pre-Release

22 06 2007

OK, this one is important… 5 min is all I got 🙂 

In another BIG community contribution, the CKS (Community Kit for Sharepoint) Team  is lounching the Community Kit for SharePoint 2.0 Pre-Release .

This CKS 2.0 Pre-Release contains the following:

  • Enhanced Blog Edition Beta 1
  • Enhanced Wiki Edition Alpha
  • ChatterBox AJAX Beta
  • Tag Cloud

A lot more is expected for the following versions, so keep an eye and if your willing, join the team. Check their site.


No news this week… no time to do it!

22 06 2007

Thsi was a highly demanding week. At least the deployment is done and by now, only tunning and small adjustments are being made. This wek the extra effort went to a “after-hours” WCF course.

Untill now, I had only read a couple of articles on WCF, mostly on what you can do and bla bla bla. Now, I’ve been looking to the “user guide” and mainly to the best practices.

Let me tell you: it is VERY powerfull and therefore, its much more vast than I expected. For you to fully dig deep into WCF, start removing the dust from distributed computing, concurrency, transactions, security and try to grab some info on SOA.

My fealing: this will be the services platform for the years to come (untill the y come up with a new one 😉 ).

I’ll try to grab some pointers to a first look into WCF and will post an update.

Why the @£$% can’t a deployment go smoothly, just for once…?

11 06 2007

Sorry about this, but I had to spill out my anger…

For the Nth time I was part of a deployment team. This time of a Moss solution; and for the same number o times, if was a living hell…

Does this happens only to me and the ones I work with? Is this some kind of bad carma that goes hoovering the poor IT guys & girls? I don’t think so. We must be doing something wrong.

There must be strict methodology to guide us in this process. The perfect solution is having development environment === qualification environment === production environment. This is not always possible, but provides the higher chances of success.

Virtualization is a big +. You can create production environment replica to both qualification and development. This is highly manageable and very dynamic, allowing easy entry of new members on the team with so little as “newsid” command. Or if you have syspreped the images, a small configuration step will solve this step. On the other hand, this usualy implies a lot of machines to maintain and therefore, a lot of time spent on managing the infrastructure. I actually worked in a development project which had about 30 machines (both physical and virtual) that implemented the infrastructure for the client network and the 7 development team elements. By the end of the project, 6 more were added when demo environments were built.

Well this is great, but it takes you a lot of time. Managing updates, syncronizing versions, solving connectivity problems.

So, its a trade. You must evaluate teh complexity of the environment, the length of the project, the complexity of the solution, etc, etc, etc.

If you read this, drop a line. Share your thoughts on this topic. Throw some like at these shades…

I’m blue 😦

Tool: Sharepoint Manager 2007

9 06 2007

Yep, here’s another tool that is present in my toolbox: Sharepoint Manager 2007. This tool, written by Carsten Keutmann, allows you to explore one Sharepoint installation and drill down from the site collection, to the leaves, with full acces to properties and definitions of all the objects.

Oh, BTW, it allows you to change part of the properties too ;).

Just be sure about what you are changing or you will end up with a ruined installation.


  • Microsoft Server 2003
  • Microsoft  .NET Framework 2.0
  • Microsoft SharePoint Services 3.0

Download available from here.

WSPBuilder perfect companion: Content Explorer

6 06 2007

While WSPuilder will build the solution package for deployment, Content Explorer will generate features with the Content Types, as well as the referenced fields and hierarchy.

The tool site is in German, so I’ll leave you with the link to the direct download.

The features are created in folders and all you have to do is to drag them into the /12/Template/Features folder that will be used afterwards by the WSPBuilder.

This one I have tested and I am using.

Just a couple of hints:

I have found that some elements and/or properties in the fields feature are not accepted. i had to manually clean the following:

  • property -> Version=””
  • property -> Aggregation=””
  • property -> webid=””
  • Element -> <customization></customization>

All these and probably more are not supported and will prevent you solution to be added.

With these tools that are appearing, we are starting to have an interesting set of tools for deployment. Nevertheless, a consolidated deployment tool is still needed…

Blessed tool: WSPBuilder

4 06 2007

If you ever had to build a deployment solution, you are probably shivering by now, just from reading this line. Any help you can get on the process is a blessed one, so here is another answer to your praires.

The tool is a WSP Builder that mirrors a “12” folder structure into a deployment package and builds the ddf and manifest.xml file for you.

I haven’t tried it yet, but is sure sounds promising. I’ll let you know soon enough!

Look for it here!


(more) SharePoint 2007 figures & numbers

4 06 2007

Going a little bit further on the topic of limitatiosn that I blogged some days ago in the post SharePoint 2007 Maximum Limitations, I found some more details (and juicy ones ..) regarding limits and figures on Sharepoint 2007. It was sposted at technet.

 Here are some tables with the main figures:

The following table lists the recommended guidelines for site objects.

Site object

Guidelines for acceptable performance Notes Scope of impact when performance degrades
Site collection 50,000 per Web application Total farm throughput degrades as the number of site collections increases. Farm
Web site 250,000 per site collection You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites. Site collection
Subsite 2,000 per Web site The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Site view
Document 5 million per library You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored. Library
Item 2,000 per view Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance. List view
Document file size 50MB (2GB max*) File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB. Library, file save performance
List 2,000 per Web site Testing indicates a reduction in list view performance beyond two thousand entries. List view
Field type 256 per list This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases. List view
Column 2,000 per document library4,096 per list This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases. Library and list view
Web Part 50 per page This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected. Page

The following table lists the recommended guidelines for people objects.

People object

Guidelines for acceptable performance Notes
Users in groups 2 million per Web site You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users.
User profile 5 million per farm This number represents the number of profiles which can be imported from a directory service, such as Active Directory, into the people profile store.
Security principal 2,000 per Web site The size of the access control list is limited to a few thousand security principals (users and groups in the Web site).

The following table lists the recommended guidelines for search objects.

Search object

Guidelines for acceptable performance Notes
Search indexes One per SSPMaximum of 20 per farm Office SharePoint Server 2007 supports one content index per SSP. Given that we recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is supported. Note that an SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.
Indexed documents 50,000,000 per content index Office SharePoint Server 2007 supports 50 million documents per index server. This could be divided up into multiple content indexes based on the number of SSPs associated with an index server.
Content sources 500 per SSP* This is a hard limit enforced by the system.
Start Addresses 500 per content source* This is a hard limit enforced by the system.
Alerts 1,000,000 per SSP This is the tested limit.
Scopes 200 per site This is a recommended limit per site. We recommend a maximum of 100 scope rules per scope.
Display groups 25 per site These are used for a grouped display of scopes through the user interface.
Crawl rules 10,000 per SSP We recommend a maximum 10,000 crawl rules irrespective of type.
Keywords 15,000 per site We recommend a maximum of 10 Best Bets and five synonyms per keyword.
Crawled properties 500,000 per SSP These are properties that are discovered during a crawl.
Managed properties 100,000 per SSP These are properties used by the search system in queries. Crawled properties are mapped to managed properties. We recommend a maximum of 100 mappings per managed property.
Authoritative pages 200 per relevance level This is the maximum number of sites in each of the four relevance levels.
Results removal 100 This is the maximum recommended number of URLs that should be removed from the system in one operation.
Crawl logs 50,000,000 Number of individual log entries in the crawl log.

The following table lists the recommended guidelines for logical architecture objects.

Logical architecture object

Guidelines for acceptable performance Notes
Shared Services Provider (SSP) 3 per farm (20 per farm maximum)  
Zone 5* per farm The number of zones defined for a farm is hard coded to 5.
Web application 99 per SSP This limit includes the number of Web applications on child farms consuming resources on this SSP.
Internet Information Services (IIS) application pool 8 per Web server Maximum number is determined by hardware capabilities.
Site collection 50,000 per Web application  
Content database 100 per Web application  
Site collection 50,000 per database  

The following table lists the recommended guidelines for physical objects.

Physical object

Guidelines for acceptable performance Notes
Index servers 1 per SSP*  
Application servers running Excel Calculation Services No limit  
Query servers No limit Because 100 content databases are supported for each query server, the number of query servers required per farm is based on the number of content databases in the farm. For example, if there are 500 content databases in your farm, you will need at least 5 query servers.
Web server/database server ratio 8 Web servers per database server The scale out factor is dependent upon the mix of operations.
Web server/domain controller ratio 3 Web servers per domain controller Depending on how much authentication traffic is generated, your environment may support a greater number of Web servers per domain controller.

You can find the full article on technet, with graphs and test environment settings that will help to complete the scenario.

Hope it helps!