SharePoint Online Learning Materials for IT Professionals

Are you an IT Professional looking to learn more about how SharePoint Online can help supplement your on-premise SharePoint 2010 Products deployment? We’ve recently released a comprehensive set of learning materials that illustrate the benefits of SharePoint Online and how you can leverage its capabilities to bring additional value to your on-premise deployment.

Video Learning Series






Narrated Presentation

Exploring SharePoint Online for IT Professionals


Microsoft SharePoint Online: An Overview for Enterprise IT Professionals

Site Recycle Bin (Service Pack 1 and CodePlex) FAQs

Do I need to uninstall the Site Recycle Bin from CodePlex if I plan to use the Site Recycle Bin in Service Pack 1?

It depends on what you’re looking for.  The Site Recycle Bin available through CodePlex will capture deleted Site Collections and Sites to disk, Site Recycle Bin in Service Pack 1 copies the Site Collections and Sites to an auxiliary SQL table until they are permanently deleted at which point are managed by Gradual Site Deletion.  Once a Site Collection or site enters this Garbage Collection phase it will be managed by the Site Recycle Bin on CodePlex and copied to disk.  In theory you could have both.  The CodePlex Site Recycle Bin to provide archival and the Site Recycle Bin in Service Pack 1 to provide quick recovery and enable Site Collection administrators to perform self-service restores.

What happens to deleted Site Collections?  Do they ever get deleted?

These objects are purged.

There already is Web application property that controls the retention period for the Site Collection level Recycle Bin.  The same property is used for the deleted Site Collections themselves; when the Site Collection was deleted prior to a specified period (30 days), the timer job permanently removes it from the Content Database.  A Site Collection in the process of being permanently removed can no longer be restored.

Service Pack 1 Move-SPSite w/ ‘shallow copy’

Service Pack 1 introduces a new method of moving Site Collections between Content Databases where RBS is used known as ‘shallow copy’.


What is ‘shallow copy’?

‘Shallow copy’ refers to moving structured content without moving the underlying unstructured content.  With SharePoint 2010 Products ‘shallow copy’ moves the structured Site Collection data across Content Databases without moving the unstructured data which is comprised of user created content such as PowerPoint Presentations, Word Documents, etc.

What is a ‘shallow copy’ migration?

‘Shallow copy’ migration refers to a migration technique in which structured Site Collection data is moved across Content Databases while the unstructured BLOB data remains untouched in its originally configured BLOB store.

What is a deep copy migration?

Deep copy refers to a migration technique is which unstructured BLOB data is passed through the Object Model when its associated Site Collection is moved across Content Databases, I.e. download and upload of BLOB data.


‘Shallow copy’ capabilities provide a number of benefits, for example, shallow copy migration enables seamless movement of Site Collections across Content Databases while improving performance through enabling the unstructured data to remain in the originally configured BLOB store.  In scenarios where the same RBS provider is configured in both the source and destination Content Database the structured Site Collection data is moved without copying the underlying BLOB data – transferring only the ownership information between Content Databases.

In many SharePoint 2010 Products deployments unstructured BLOB data comprises 80% or more of the total content, ‘shallow copy’ helps administrators avoid deep copy migration significantly reducing the time required to move Site Collections between Content Databases.


The following prerequisites are required to implement ‘shallow copy’ migrations.

SQL Server 2008 R2 Public Cumulative Update
SharePoint Server 2010 Service Pack 1

Administrators can leverage ‘shallow copy’ functionality in Service Pack 1 through both the Object Model and Windows PowerShell using the Move-SPSite Windows PowerShell CmdLet with the -RbsProviderMapping parameter.  The -RbsProviderMapping parameter defines the mapping between the RBS providers in the source and destination Content Databases.

Move-SPSite -Identity siteUrl -DestinationDatabase databaseName -RbsProviderMapping
    @{"sourceProvider1"="targetProvider1", "sourceProvider2"="targetProvider2"}

When using the -RbsProvideMapping parameter the ownership of the RBS pool (subset of the BLOB store documents) used by the specified Site Collection is transferred from the source to the destination Content Database without moving the underlying unstructured data associated with that Site Collection.

‘Shallow copy’ is also an efficient migration method when moving from EBS to RBS.  In an EBS to RBS scenario the EBS token is moved from the source to the destination Content Database.

For additional information on Remote BLOB Store Architecture see

For additional information on the Move-SPSite CmdLet see

New Governance Resources from Microsoft IT

Microsoft IT has released several new resources related to the governance of Microsoft’s SharePoint service.

Implementing SharePoint 2010 Site Governance and Lifecycle Management 

Webcast: How Microsoft IT Handles SharePoint 2010 Governance and Life Cycle Management (Level 200) (

Now Serving Larger Databases…

Today we are announcing some important and exciting changes to our software boundaries and limits for SharePoint 2010 Products, in summary SharePoint 2010 Products will now support content databases up to 4TB.  However, prior to considering multi-terabyte databases you should thoroughly review the following whitepapers:

Managing multi-terabyte databases with SharePoint 2010 (


Managing large content databases with SharePoint 2010 requires careful planning and consideration to include capacity management, performance, and data protection.  This whitepaper provides guidance to support these considerations to include additional resources to support this guidance.

Database Maintenance for SharePoint 2010 Products (


This white paper provides information and guidelines for maintaining the databases that host Microsoft® SharePoint® 2010 data and configurations. It describes and provides examples of the database maintenance tasks that we recommend when using SharePoint 2010.

Before you implement any database maintenance tasks or modify your SharePoint 2010 databases, read the following support article: Support for changes to the databases that are used by Office server products and by Windows SharePoint Services (

To learn more about this announcement see the SharePoint Team Blog at

To learn more about the new software boundaries and limits see SharePoint Server 2010 capacity management: Software boundaries and limits at