Last Tuesday, Microsoft released Service Pack 1 (SP1) for SharePoint 2010. It contains a lot of important fixes that improve the SharePoint experience, performance, security etc. And include the following new features:
- Support for SQL Server Code Name “Denali”
SP1 provides support for running SharePoint 2010 with SQL Server Code Name “Denali” in addition to providing ongoing support for SQL Server 2008 and SQL Server 2005. For more information about the improvements and new features that are part of SQL Server Codename “Denali”, see the SQL Server product Web site (http://go.microsoft.com/fwlink/LinkId=221774).
- Shallow copy functionality
Shallow copy is a migration technique in which structured site collection data is moved across content databases while the unstructured data remains untouched in its originally configured BLOB store. In scenarios where the same remote blob storage (RBS) provider is configured in both the source and destination content database, the structured site collection data is moved without copying the underlying unstructured data. Instead, only the ownership information is moved between content databases.
In SP1, new shallow copy functionality is implemented with the Move-SPSite Windows PowerShell cmdlet. This cmdlet enables you to move site collections between content databases without moving the underlying unstructured data such as Microsoft Word documents and PowerPoint presentations. Shallow copy significantly increases performance and reliability for organizations using RBS by simply updating the pointers to those objects in the destination content database.
Shallow copy is not supported with the local FILESTREAM provider.
Prerequisite:
In order to use shallow copy, you must have installed the Microsoft SQL Server 2008 R2 Remote Blob Store. The Remote Blob Store is included in the Microsoft SQL Server 2008 R2 SP1 Community Technology Preview Feature Pack (http://go.microsoft.com/fwlink/LinkId=221775).
Performing a shallow copy:
You perform a shallow copy by using one of the following methods:
- Using the Object Model.
- Using the Move-SPSite cmdlet. In this cmdlet, the RbsProviderMapping parameter defines the mapping between the RBS providers in the source and destination content databases. The syntax of this cmdlet is as follows:
Move-SPSite -Identity siteUrl -DestinationDatabase databaseName ?RbsProviderMapping @{“sourceProvider1″=”targetProvider1″,”sourceProvider2″=”targetProvider2”}
- Site-level recycle bin
The site Recycle Bin enables self-service recovery of site collections and sites. In SP1, administrators can quickly and easily recover site collections and sites that have been accidentally deleted by their owners. The recovery process is similar to that of the Recycle Bin for lists, libraries, and documents.
- Improvements to storage management (StorMan.aspx)
In previous versions, the page StorMan.aspx (Storage Space Allocation) enabled granular management and insight into storage. For example, the page would list the 100 largest documents or document libraries. With this information, end-users could easily clean up their sites by deleting the large content that they no longer needed.
The StorMan.aspx page was removed in SharePoint 2010. For more information, see http://support.microsoft.com/kb/982587. SP1 introduces an improved StorMan.aspx, enabling users to better understand what is using up their quota and to act upon that information in order to reduce the size of their sites.
- Cascading filters for Performance Point services
New cascading filter support enables you to pass the value of one filter to another.
- Additional browser support
SP1 provides support for Internet Explorer 9 in Internet Explorer 8 Standards Mode and also provides support for the Google Chrome browser.
For a complete list of supported browsers, see Plan browser support (SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkID=221778) and Plan browser support (SharePoint Foundation 2010) (http://go.microsoft.com/fwlink/?LinkID=221779).
IMPORTANT NOTE from Microsoft Office Sustained Engineering Team
It is strongly recommended to install the?June 2011 Cumulative Update (CU) immediately after the installation of Service Pack 1. The June Cumulative Update includes several important security and bug fixes that are not included Service Pack 1.
The difference between SP1 and the June CU
- SharePoint 2010 SP1 contains all SharePoint updates published through the April 2011 Cumulative Update in addition to other fixes that were applied specifically to SP1 during its development. SP1 is a baseline, and that baseline is tied to Service Pack Life Cycle Policy.
- The June Cumulative Update is the first Post-SP1 build released to customers. It contains new fixes to issues raised through various escalation channels and through our support organization. The June CU is based on Service Pack 1, but it adds new updates to?some of (not all) the packages that SP1 installs.
In the recommendation of SharePoint team, we should install the service packs in the following order on every server in the farm.
1.Service Pack 1 for SharePoint Foundation 2010
2.Service Pack 1 for SharePoint Foundation 2010 Language Pack (if applicable)
3.Service Pack 1 for SharePoint Server 2010
4.Service Pack 1 for SharePoint Server 2010 Language Pack (if applicable)
The SharePoint 2010 Products Configuration Wizard or “psconfig?cmd upgrade?inplace b2b-wait” should be run once on every server in the farm following the final update installed.
The version of content databases will be 14.0.6029.1000 (see the Figure 1) after successfully installation. For more in-depth guidance for the update process, we recommend reviewing the following articles.?These articles provide a correct way to deploy updates and identify known issues (and resolutions).
Figure 1
Refer to:
Service Pack 1 (SP1) for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 (whiter paper) (http://www.microsoft.com/download/en/details.aspx?id=26573)
Microsoft Office Sustained Engineering Team (http://blogs.technet.com/b/office_sustained_engineering/archive/2011/06/29/sharepoint-2010-sp1-and-the-june-cumulative-update-for-sharepoint-2010.aspx)