Create Site Collection in Separate Content Database in SharePoint

Problem:

When a “Site Collection” is created in a web application, then the proceeding Site Collections created in the same “Web Application” will use the Same Content DB.

This creates problems in the following scenarios:

1. Size of the one Site Collection grows large then it will affect the other Site Collection too. The
reason being maximum size of a Content DB for a Site Collection with good performance is 200 GB
(referred some MSDN articles).

2.  During migration/archival/splitting of content DB.

Solution:

The solution for the above problem is to “Create Site Collections with Separate Content DB for each Site Collection”.

But by default SharePoint allows you to create new site collections in the Same Content DB which is used by the web application (one created first – Top Level Site Collection)

Using Central Administration page:

1.   Suppose that we have created a Top Level Site Collection with content DB named “WSS_Content_1000”. Now our scenario is to create a new site collection in the same web application with different content db.

2. Now navigate to Central Admin -> Application Management -> SharePoint Web Application Management -> Content databases

3. By using the option Add a content database in the menu, create a new content DB named “WSS_Content_1050”

 6. Now, you can see the database (WSS_Content_1000) in the stopped state: 

 7. Now, try creating a new Site Collection in the same web application. “Your new site collection will be forced to create in the Content DB which is available in the web application” (in our case it is WSS_Content_1050).

8. Now, change the status of the first content db to Ready state.

9. Now to check whether our new site collection is created in different db’s go to Central Administration -> Application management -> Site collection list. “You can see two site collections in two different databases” as shown below:

     ØTop level site collection created in WSS_Content_1000 db

     ØTop level site collection created in WSS_Content_1050 db

10. As shown in the above screenshot, we are able to create a new site collection with a new Content DB using the above method.

Read More

Remote Blob Storage (RBS) in SharePoint 2010

In this article, we will know about a new feature in SharePoint 2010 which allows the remote storage in SharePoint.

What is Remote BLOB Storage?
     Ø  BLOB – Binary Large Object

Ø  Remote BLOB Storage (RBS) is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server.

Ø  It can be run on servers with Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition.

Ø  RBS is not supported for Microsoft SQL Server 2005.

Ø  In Microsoft SharePoint Server 2010, RBS can be used for content databases only.

Why RBS?

It provides the following benefits:

Ø  BLOB data can be stored on less expensive storage devices that are configured to handle simple storage.

Ø  The administration of the BLOB storage is controlled by a system that is designed specifically to work with BLOB data.

Ø  Database server resources are freed for database operations.

When to Go for RBS?

Ø  Large Database of Mostly Binary Data

Ø  Digital Asset Management Databases

Ø  When Storage Tiers Need to be Implemented

Ø  When Storage Needs to be Optimized

You can expect to benefit from RBS in the following cases:

Ø  The content databases are larger than 500 gigabytes (GB).

Ø  The BLOB data files are larger than 256 kilobytes (KB).

Ø  The BLOB data files are at least 80 KB and the database server is a performance bottleneck. Then, RBS reduces the both the I/O and processing load on the database server.

RBS Advantages over EBS (External Blob Storage)

Hope this explains about the basics of RBS in SharePoint 2010.

I came across a good article explaining about Configuring Remote Blob Storage for SharePoint 2010. Here is the link.

Happy Sharing!

Read More

Exporting SharePoint User Groups with Group Names

In the article Exporting SharePoint User Groups into Excel, we have learned about exporting the SharePoint user groups into excel. Here we are able to export all the users in a SharePoint site but we are unable to sort the users with the group name.

In this article, we will learn a small work around filter the users with the group name.

We can use SQL Query to fetch this data.

Connect to the SQL server and open a new query in the content database where your SharePoint site resides.

The SharePoint content DB does not expose the tables (for lists, libraries, users, etc.) in the database directly.

The below is the query which will fetch all the users in the SharePoint site with the user groups in a separate column in the result.
SELECT dbo.Groups.ID, dbo.Groups.Title, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_Login FROM dbo.GroupMembership INNER JOIN dbo.Groups ON dbo.GroupMembership.SiteId = dbo.Groups.SiteId INNER JOIN dbo.UserInfo ON dbo.GroupMembership.MemberId = dbo.UserInfo.tp_ID

Hope this helps you!

Please free to comment. Always your comments makes me to write more!

Read More