I had the FAST Search server 2010, SharePoint 2010 and SQL Server 2008 R2 installed on a single demo machine. Though this is not something which Microsoft recommends, it was very important when you visit clients for showing a demo showcasing the capacity of FAST.
When I tried to verify the memory and CPU consumption in the Task Manager, it did not took a long time to understand that the SQL Server and a FAST Search Server exe was one of the major culprits in bringing the system down on many of the occasions.
It appeared that continuously adding managed properties continuously across all the demos was leading to a continuous update in the index for the properties, which led to a high memory and CPU usage.
To overcome this, you should perform the following steps:
This should handle most of the issues related with high CPU and memory usage.
I had created a SharePoint 2010 Web Part which was using the ASP.NET List view. The code compiled fine and was deployed properly. However, when I was trying to add the web part to the Web part page, I was getting the following error:
Open the web.config and add the following entry in <Controls>
<add tagPrefix=”asp” namespace=”System.Web.UI.WebControls” assembly=”System.Web.Extensions, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
You may run across scenarios where you would like to create an entirely new infrastructure for the SharePoint 2010 instances. In such scenarios, the Attach Database and Upgrade method can be applied.
The Database upgrade method upgrades only the content of the database and does not upgrades any of the settings on the new SharePoint 2010 Server.
The complete process of Database Attach and upgrade can be accomplished using the following steps:
1) Take a backup of the Content database of the SharePoint 2007 Server. you should take the backup of the following:
By default, the SharePoint 2010 is available only in 64 bit mode. To be able to upgrade the SharePoint 2007 32 bit to SharePoint 2010, you will first need to upgrade your SharePoint 2007 32 bit to SharePoint 2007 64 bit if you are interested in migrating only some of the SharePoint sites.
The stsadm command for taking a backup of a site
stsadm –o backup –url <url of the SharePoint 2007 site> –filename <Path and file name of the backup file>
you can also use –force switch to force the backup process in case of any issues.
If you want to migrate the entire Farm, you can take a backup of the entire 32 bit farm and restore it in SharePoint 2007 64 bit.
you can use the stsadm command to backup the entire farm
stsadm -o backup -directory <\\server name\folder name> -backupmethod full
you can take a backup of the SharePoint 32 bit site and restore it on a 64 bit site.
if your SharePoint 2007 server does not have sp2, then you will need to update the SP2 on the SharePoint box before you evaluate the feasibility of upgrading to SharePoint 2010.
The process of taking a backup of the database in SQL Server 2008 is as follows:
1) Start the SQL Server Management studio
2) Right click on the Database that needs to be backed up
3) Select Backup
4) Provide a valid path to save the backup.
you can restore a SharePoint backup of a SharePoint Site using the following stsadm command
stsadm –o restore –url <url of web application> –filename <Full path of the backup file>
you can run the stsadm command on the SharePoint 2007 server to verify the upgrade readiness for the sites in the SharePoint Server. if the installation is a farm installation, the command should be run on the SharePoint box hosting the “Central Administration”
This command was first introduced with wss 3.0 sp2. This command is intended to run a set of rules that will assist the administrators to prepare the existing sharepoint 2007 installation to a future sharepoint 2010 version.
The parameter –rulefiles takes a valid rule file and is an optional parameter. It requires a quoted, delimited (comma or semicolon) list of rule file names. By default this command is run for all the available rule files. The rule files are available in the 12 hive\config\preupgradecheck folder.
The parameter –listrulefiles lists all rule files without executing the check routine. This is also an optional parameter.
The parameter –localonly is a required parameter and checks the local server with the rules marked as local only and evaluates them.
It also generates a detailed html report in the logs folder
You can check the microsoft knowledgebase for corrective actions.
For additional details on this you can check my blog https://sharepointtech.wordpress.com/2010/10/17/sharepoint-2010-migration-part-i/
Add Pre Checks before attaching this backup on the new SharePoint 2010 site
A SharePoint Site may contain one or more of the following additional components:
All such items needs to be manually migrated and applied on the SharePoint 2010 Website.
These items needs to be applied before attaching the SharePoint Database.
To understand the feasibility and custom items required for migrating, you can use the PowerShell Command Test-SpContentDatabase.
Test-SPContentDatabase –Name <database name> -WebApplication <Web application URL> [-ServerInstance <ServerInstanceName>] [-DatabaseCredentials <Domain\username>]
If there is any Pre requisite item that needs to be applied on the server before the database is attached then you will need to apply all such items to the candidate web application.
Once these checks are applied then you can attach the database.
If the SharePoint 2007 site contains multiple databases, then the order of attaching the content database is as follows:
The process of attaching the content DBs in the SharePoint 2010 Web Application should be done through STSADM tool. For Attaching the Content DB to a SharePoint 2010 Web application, you should perform the tasks in the following order:
To upgrade the MySite to SharePoint 2010, you should perform the following activities
The limitation of indexing Files greater than 16 MB in size still exists in SharePoint 2010. The limitation was enforced to avoid network clogging and improve SharePoint performance.
In all such scenarios, where the file format is Compatible to SharePoint and the size of the file is larger than the max threshold size, the indexer is able to index the metadata of the file. however, the content of the file is not indexed.
For all files which are smaller than 16 MB in size and the file format is compatible to SharePoint, the content as well as the metadata of the file is indexed.
The major problem is that in SharePoint 2007, all such scenarios where the File Size was greater than 16 MB, were logged in as warning in the Crawl logs. However, there is no such warning generated in case of SharePoint 2010 and hence it is very difficult to understand the issue.
This whole behavior is guided by two registry values:
By default , the MaxDownloadSize is 16 MB and the MaxGrowthFactor is 4 MB in Size. This basically implies that:
Before SharePoint 2010, this settings were modified by modifying the registry information at
HKEY_LOCAL_MACHINE -> SOFTWARE –> Microsoft –> Office Server -> 12.0 –> Search –> Global –> Gathering Manager
However for some reasons these settings don’t persist when applied in SharePoint 2010 environment. you need to alter the settings using the PowerShell.
The max value supported by “MaxDownloadSize” is 2 GB.
The solutions developed in VSeWSS extensions are not directly portable into Visual Studio 2010.
To Run the VSeWSS Projects in Visual Studio 2010, an import tool has been released in MSDN which helps in executing the VseWSS Projects. This tool gets installed as a Visual Studio 2010 add in and provides a new SharePoint Project Template .
The tool is available at the following location:
All the discussions related with this tool is available at
During an in place upgrade process, the entire SharePoint 2007 box is upgraded to SharePoint 2010. The up gradation process upgrades the entire SharePoint 2007 installation.
For upgrading a SharePoint standalone installation, the process is as follows: