The official blog for Windows Server Essentials and Small Business Server support and product group communications.
[Today's post comes to us courtesy of Shawn Sullivan from Commercial Technical Support]
For those of you who are operating with a WSS 3.0 site that has a content database approaching or larger than 10GB, you will have to take database size limits into account if you are planning a migration to SBS 2011. SBS 2011 setup installs Sharepoint 2010 Foundation by default, which uses a named instance of SQL 2008 R2 Express to hold the configuration, content, and search databases. Whereas WSS 3.0 uses the Windows Internal Database version of SQL which does not impose a database size limit, SQL 2008 R2 Express imposes a 10GB limit. In preparation for the migration, when you run the prescan utility on a WSS 3.0 content database that is approaching this threshold, two of its checks will fail:
Failed: Databases within this farm are hosted on Windows Internal Database and are larger than or close to 4GB in size.
Failed: Site Collections within this farm are hosted on Windows Internal Database and are larger than or close to 4GB in size.
Note: The 4GB limit mentioned in the rule does not apply to SQL 2008 R2 Express, which increased the limit to 10GB. The 4GB limit is imposed by SQL 2008 Express, which SBS 2011 does not use.
There are two options available if you intend to migrate this content database off of WSS 3.0. You can either try using Remote Blob Storage (RBS) or you can purchase SBS 2011 Premium and upgrade to SQL 2008 R2 Standard. The problem with RBS is that it is so dependent on what is actually in the database that it is not guaranteed to work around the size limit issue and there is still a limit on how large your data can grow. Although a deep technical discussion about RBS is not within the scope of this post, three quick facts from the link above are important to mention here:
For these reasons, we do not recommend using RBS and instead urge you to upgrade to SQL 2008 R2 Standard. The remainder of this post will show you how to accomplish this.
As mentioned before, this edition of SQL is included with SBS 2011 Premium for you to either install on the SBS server itself or onto a second machine running Windows Server (2008 R2 media is also included with Premium). In this part, I will demonstrate how to upgrade the existing R2 Express instance of SharePoint to R2 Standard in preparation for the migration. Subsequent posts in this series will demonstrate how to install a new R2 Standard instance on the second server and how to migrate the content database to it.
At this point, you will be ready to pick up at this step on the SBS 2011 Migration whitepaper. The next part of this series will cover installing the SQL 2008 R2 Standard instance on server two.