Administration, SharePoint

SharePoint 2010 Cumulative Updates and Service Packs

Updated June 29, 2011

SharePoint Server 2010 Cumulative Updates and Service Packs

File Version Description Downloads and Documentation
14.0.5114.5003 June 2010 Cumulative Update KB983497
KB2124512
KB2182938
KB2204024
KB2281364
14.0.5123.5000 August 2010 Cumulative Update KB2352342 
KB2352355
14.0.5128.5000 October 2010 Cumulative Update KB2394320
14.0.5130.5002 December 2010 Cumulative Update KB2459257
14.0.5136.5002 February 2011 Cumulative Update KB2475878
14.0.5138.5001 April 2011 Cumulative Update KB2512800
14.0.6029.1000 Service Pack 1 KB2460045
14.0.6106.5000 June 2011 Cumulative Update KB2356599

SharePoint Foundation 2010 Cumulative Updates and Service Packs

File Version Description Downloads and Documentation
14.0.5114.5003 June 2010 Cumulative Update KB2028568
14.0.5123.5000 August 2010 Cumulative Update KB2352346
14.0.5128.5000 October 2010 Cumulative Update KB2394323
14.0.5130.5002 December 2010 Cumulative Update KB2459125
14.0.5136.5002 February 2011 Cumulative Update KB2475880
14.0.5138.5001 April 2011 Cumulative Update KB2512804
14.0.6029.1000 Service Pack 1 KB2460058
14.0.6106.5000 June 2011 Cumulative Update KB2356591

Resources

SharePoint 2010 Products Updates Resource Center

Standard
Administration, SharePoint

Service Pack 1 – Site Recycle Bin

Site Recycle Bin

Service Pack 1 introduces long awaited Site Recycle Bin functionality that enables self-service recovery of site collections and sites. In the past IT Professionals were tasked with restoring entire databases to recover deleted site collections and sites and would generally require expensive restore environments to support the task. Now in Service Pack 1 administrators can quickly and easily recover site collections and sites accidentally deleted by their owners in a process similar to that of the Recycle Bin we have for Lists, Libraries, and Documents.

The Site Recycle Bin leverages Gradual Site Delete through implementing a delay between Gradual Site Delete and permanent deletion of the deleted Site Collection.

User Interface

Users are presented with new text when deleting Sites instructing users that all site content will be sent to the site collection Recycle Bin (see Figure 1 Deleting http://sharepoint.contoso.com/sites/customers/Fabrikam).

Figure 1 Deleting http://sharepoint.contoso.com/customers/Fabrikam

DeleteSite1

Site Restore

Site Collection administrators can restore deleted Sites in the same manner through which Items, Lists, and Libraries are restored through the Recycle Bin; however, the size of the Site is not reported through the user interface which differs from content to include Items, Lists, and Libraries.  To restore a Site, the Site Collection administrator selects the checkbox next to the Site to be restored and selects Restore Selection (see Figure 2 Restoring http://sharepoint.contoso.com/sites/customers/Fabrikam).

Figure 2 Restoring http://sharepoint.contoso.com/sites/customers/Fabrikam

DeleteSite2

NOTE

In the event the Site has been recreated using the same Url, the Site must first be renamed or deleted for the restore to succeed; however, when restoring My Site personal sites, any newly created My Site personal site using the same Url as the Site to be restored is overwritten.

The Site Recycle Bin in SharePoint 2010 leverages the retention policies specified at the Web application level for the Recycle Bin in SharePoint 2010.

Object Model

SPWebApplication.GetDeletedSites(Url) returns a SPDeletedSitesCollection that contains all SPDeletedSites with the specified Url.

SPDeletedSiteCollection

SPDeletedSiteCollection represents a collection of SPDeleteSite objects or Site Collections that are associated with a particular Web application, including a top-level Web site and all its sub-sites.

SPDeletedSite

SPDeletedSite represents a collection of deleted sites in a Web application, including a top-level Web site and all its subsites.

SPDeletedSite Properties

SiteId returns the Site Id (GUID) associated with the specified SPDeletedSite.

Url returns the Url associated with the specified SPDeletedSite.

ContentDatabaseId returns the Id of the Content Database associated with the deleted Site.

Restore restores the deleted site collection.

To learn more about Service Pack 1 for SharePoint 2010 see my post on the SharePoint Team Blog at http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=973.

Standard
Administration, SharePoint

Service Pack 1 – Storage Metrics (StorMan.aspx)

In SharePoint 2010 we removed StorMan.aspx (Storage Space Allocation) (see http://support.microsoft.com/kb/982587/EN-US) which in previous versions of SharePoint enabled granular management and insight into storage. For example, the page would show you the top 100 documents or document libraries in terms of size. With that information end users could the page to clean up content from their site(s) by deleting the large content that they no longer needed. In Service Pack 1 we are bringing back an improved StorMan.aspx, enabling users to better understand where their quota is going and act upon that information to reduce the size of their sites.

Storage Metrics provide insight into how storage is being used across Site Collections and Sites enabling administrators and owners to quickly identify content that can be archived or removed in order to remain within their allocated quotas.

To begin using Storage Metrics select Site Actions, and then click Site Settings.

From Site Settings select Storage Metrics under Site Collection Administration (see Figure 1 Site Settings http://sharepoint.contoso.com/).

Figure 1 Site Settings http://sharepoint.contoso.com/

StorMan1

Storage metrics will be displayed for the selected Site Collection/Site (see Figure 2 Storage Metrics http://sharepoint.contoso.com/).

Figure 2 Storage Metrics http://sharepoint.contoso.com/

StorMan2

To learn more about Service Pack 1 for SharePoint 2010 see my post on the SharePoint Team Blog at http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=973.

Standard
SharePoint

Service Pack 1 for SharePoint 2010 Products

Service Pack 1 for SharePoint 2010 Products is now available for download.

SharePoint Server 2010

Service Pack 1 for Server Language Pack 2010

SharePoint Foundation 2010

Service Pack 1 for SharePoint Foundation 2010 Language Pack

To learn more about what’s new in Service Pack read the Service Pack 1 for SharePoint Foundation 2010 and SharePoint Server 2010 whitepaper at http://go.microsoft.com/fwlink/?LinkId=221773.

Standard
Administration, SharePoint

Announcing the SharePoint Diagnostic Studio

One of the most challenging aspects of maintaining a SharePoint deployment is understanding why certain events have transpired in the environment, often IT Professionals and Developers only have access to when an event occurred and are tasked with parsing Performance Counters, Event and Diagnostic logs, or executing Transact-SQL statements against the Usage database to put the what and why to the when.  These tasks are typically accomplished through an array of tools such as Excel, Log Parser, SQL Server Management Studio…read more on the SharePoint Team Blog.

Standard
Administration, SharePoint

FILESTREAM with SharePoint 2010

FILESTREAM is a new feature in SQL Server 2008 that enables the storage of unstructured data on a NTFS file system. FILESTREAM (local or remote) is supported in SharePoint 2010 as one mechanism of reducing capital expenditures through enabling the storage of large binary unstructured data on content addressable or commodity storage.

Unstructured Data
Unstructured data refers to information…read more on the SharePoint Team Blog.

Standard
Administration, SharePoint

FILESTREAM and SharePoint 2010

FILESTREAM is a new feature in SQL Server 2008 that enables the storage of unstructured data on a NTFS file system.  FILESTREAM (local or remote) is supported in SharePoint 2010 as one mechanism of reducing capital expenditures through enabling the storage of large binary unstructured data on content addressable or commodity storage.

Unstructured Data

Unstructured data refers to information that does not adhere to a defined model or does not fit well into relational tables in SharePoint unstructured data can refer to Microsoft Office document file formats, video, audio, and related file types.

Structured Data

Structured data in SharePoint refers to the metadata associated with its corresponding unstructured data or BLOB.  Relational databases are most often cited as examples of structured data.

SQL Server and Unstructured Data Storage

There are three (3) approaches to storing unstructured data with SQL Server, RBS, SQL BLOB, and FILESTREAM:

  • Remote BLOB Storage (RBS) in which SharePoint relies on a new layer in SQL Server to read or update BLOB data stored outside of the database on separate BLOB Stores (file system or dedicated BLOB stores)
  • SQL BLOB which refers to traditional BLOB storage with SharePoint, BLOB data is stored along side the structured metadata in the Content Database
  • FILESTREAM

FILESTREAM Overview

FILESTREAM is implemented on the varbinary(max) datatype instructing the database engine to store unstructured data on the file system through a FILESTREAM filegroup that contains file system directories instead of the files themselves also known as data containers.  Data containers are the interface between database engine storage and file system storage.  varbinary is the binary data type designation for binary large objects stored in SharePoint 2010 content databases and refers to variable-length binary data. (MAX) refers to a value that max indicates that the maximum storage size is 2^31-1 bytes or otherwise 2GB.  Remote BLOB Storage does not provide a mechanism to exceed to the 2GB file size limit imposed by SharePoint.

In SharePoint 2010 remote BLOB data is referenced by a unique identifier in content databases configured for RBS (see illustration).

FILESTREAM

FILESTREAM offers several benefits as related to performance 1) FILESTREAM uses the NT system cache for caching file data reducing the effect that FILESTREAM data has on Database Engine performance and 2) the SQL Server buffer pool is not used; therefore, memory is available for query processing.

FILESTREAM provides optimum value in scenarios where SharePoint is used to storage large BLOB data such as video files that will benefit from FILESTREAM or BLOB data that exceeds 1MB.

FILESTREAM and Business Continuity Management

Database mirroring does not support FILESTREAM since a FILESTREAM filegroup cannot be created on the principal server and database mirroring cannot be configured for a database that contains FILESTREAM filegroups. If the FILESTREAM provider is used to store BLOB data locally (within the same content database) the database cannot be configured for database mirroring.

If the FILESTREAM provider is configured to store the BLOB data within a separate SQL database or when using a 3rd party BLOB store, the content database can be mirroring; however, database mirroring will apply only to the content database and not the BLOB data. The BLOB data needs to be handled separately and kept in sync with the associated metadata (content database). For FILESTREAM BLOB databases, this can be done through log shipping.

To learn about the differences between FILESTREAM and SQL Server Remote BLOB Store see also http://blogs.msdn.com/b/sqlrbs/archive/2009/11/18/sql-server-remote-blob-store-and-filestream-feature-comparison.aspx.

The instructions that follow are designed to be used on a single-server deployment for demonstration purposes and implements the local FILESTREAM Provider.

Enable FILESTREAM on the target SQL Server Instance

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 R2, point to Configuration Tools, and then click SQL Server Configuration Manager.
  2. In the list of services, right-click SQL Server Services, and then click Open.
  3. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
  4. Right-click the instance and then click Properties.
  5. In the SQL Server Properties dialog box, click the FILESTREAM tab.
  6. Select the Enable FILESTREAM for Transact-SQL access check box.
  7. If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
  8. If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
  9. Click Apply.
  10. In SQL Server Management Studio, click New Query to display the Query Editor.
  11. In Query Editor, enter the following Transact-SQL code:

EXEC sp_configure filestream_access_level, 2

In Query Editor, enter the following Transact-SQL code:

RECONFIGURE

Provision the RBS Data Store

  1. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
  2. Expand Databases.
  3. Select the content database for which you want to create a BLOB store, and then click New Query.
  4. In SQL Server Management Studio, click New Query to display the Query Editor.
  5. In Query Editor, enter the following Transact-SQL code:

use [Database Name]

if not exists (select * from sys.symmetric_keys where name = N’##MS_DatabaseMasterKey##’)create master key encryption by password = N’Admin Key Password !2#4′

In Query Editor, enter the following Transact-SQL code:

use [Database Name]

if not exists (select groupname from sysfilegroups where groupname=N’RBSFilestreamProvider’)alter database [Database Name] add filegroup RBSFilestreamProvider contains filestream

In Query Editor, enter the following Transact-SQL code:

use [Database Name]

alter database [Database Name] add file (name = RBSFilestreamFile, filename = ‘c:BlobStore’) to filegroup RBSFilestreamProvider

Install the Microsoft SQL Server 2008 R2 Remote Blob Store

Download the x64 package for the Microsoft SQL Server 2008 R2 Remote Blob Store from the Microsoft SQL Server 2008 R2 Feature Pack at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en.

Open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:

msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<Database Name>" DBINSTANCE="<Instance Name>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1

NOTE

Specify the full path to RBS.MSI in the above state, i.e. C:UsersAdministratorDesktopRBS.MSI. Replace the values for DBNAME and DBINSTANCE to match your environment.

Enable Remote BLOB Storage

  1. On the Start menu, click All Programs.
  2. Click Microsoft SharePoint 2010 Products.
  3. Click SharePoint 2010 Management Shell.
  4. In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to set the content database to be configured:

$database=Get-SPContentDatabase –Identity “Database Name”

In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to gets the object that holds settings that determine how the content database uses Microsoft SQL Server Remote Blob Storage:

$rbs=$database.RemoteBlobStorageSettings

In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to determine if RBS has been installed for the selected content database:

$rbs.Installed()

NOTE

The result of $rbs.Installed() should be True, if the result is False, verify RBS.MSI has been installed successfully by reviewing rbs_install_log.txt. Ensure the install statement was running In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to enable RBS for the selected content database:

$rbs.Enable()

In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to set the RBSprovider for the selected content database:

$rbs.SetActiveProviderName($rbs.GetProviderNames()[0])

$rbs

NOTE

The result of $rbs should be:

Enabled

ActiveProviderName

MinimumBlobStorageSize

UpgradePersistedProperties

True

FileStreamProvider

0

()

Table 1

Appendix for Table 1

Enabled specifies whether or not RBS has been enabled for the selected content database.

ActiveProviderName is name of the SQL Remote Blob Storage provider new files will be stored in. This will be null if new files will not be stored using SQL Remote Blob storage.

MinimumBlobStorageSize refers to the minimum size a BLOB may be to be considered RBS storage worthy, BLOB data exceeding the specified MinimumBlobStorageSize will be stored in the RBS data store.

FILESTREAM performance data shows BLOB data exceeding 1MB provides the most efficient streaming performance.   See also http://msdn.microsoft.com/en-us/library/cc949109(SQL.100).aspx.

FILESTREAM Performance

To configure the MinimumBlobStorageSize:

  1. On the Start menu, click All Programs.
  2. Click Microsoft SharePoint 2010 Products.
  3. Click SharePoint 2010 Management Shell.
  4. In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to configure the MinimumBlobStorageSize at 1MB:

$database = Get-SPContentDatabase “Database Name”

$database.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576

$database.Update()

UpgradePersistedProperties specifies the collection of field names and values for fields that were deleted or changed.

Validate Installation

To validate the FILESTREAM configuration and RBS installation:

  1. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
  2. Expand Databases.
  3. Select the content database for which you want to create a BLOB store, and then click New Query.
  4. In SQL Server Management Studio, click New Query to display the Query Editor.
  5. In Query Editor, enter the following Transact-SQL code:

USE [Database Name]

SELECT * FROM dbo.DatabaseInformation

Confirm that both the RBSCollectionId and RBSProvider rows are available.

Test the RBS Data Store

  1. Select a desired Document Library on a site in the configured content database.
  2. Upload a file that is greater than 1 MB.
  3. On the computer that contains the RBS data store, click Start, and then click Computer.
  4. Browse to the RBS data store directory.
  5. Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly.

The data store directory structure will appear similar to that in the following diagram.

FILESTREAM

NOTE

In the event error "The URL ‘<Document Library>/File’ is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.” is displayed when uploading documents greater than the configured MinimumBlobStorageSize open SQL Server Configuration Manager and enable Enable FILESTREAM for file I/O streaming access and restart the SQL Server (MSSQLSERVER) service.

Additional Resources

Standard