In a previous post I spoke about how importance of pre-populating SharePointâ€™s Content Databaseâ€™s UserInfo table with users for landing/root (and/or very popular) sites just before a large release of a new SharePoint web application. While I did mention the API you could call to make all this happen I did not provide any tooling. This post is about a small tool I wrote, which at this point has been used with a couple of customers, to pre-populate UserInfo tables.The tool itself comes in two flavors â€“ one for MOSS 2007 and the other for SharePoint 2010 Server. Both flavors allow you to export users from the User Profile Store to a flat file which can then be imported in a manner which populates the UserInfo table. In addition, the SharePoint 2010 version supports both Windows and Claims users.
When an authenticated user, whom has never visited a site collection, first visits a site there are a number of tables within the Content database which must be updated. This activity can be expensive and performance can suffer when the site collection is the root of a web application which has just been announced or released for the first time into production. In fact, I have seen first hand this behavior take down a very large SQL server upon initial launch of a large intranet site to the point we had to roll back and I have teammates which have had the same experience (hence this post).
As most of you will know the SharePoint Product Group (PG) released a set of templates for WSS 3.0, known as the FAB40, to assist in addressing common business scenarios. These templates for WSS 3.0 can be downloaded in a single package here. But for those of us running SharePoint 2010 Microsoft is not planning to release new versions of these templates for SharePoint Server 2010 or SharePoint Foundation 2010.