Jean Paul's Blog

There are 2 types of People in the World, One who Likes SharePoint and..

  • Microsoft MVP

  • MindCracker MVP

  • CodeProject MVP

  • eBook on SharePoint 2010

  • eBook on Design Patterns

  • eBook on Windows Azure

  • NLayers Framework @ CodePlex

  • MSDN Forums

  • .Net vs. Java

    Due to Public Demand

Posts Tagged ‘storage’

Hard Disk Standards

Posted by Jean Paul on February 21, 2014

SharePoint to the core is a Content Management System & Hence we need to focus on the speed/size/cost of underlying Hard Disks.

SharePoint stores contents in the databases.  The content can be divided as:

  1. Structured (list, document library columns)
  2. BLOBs (which can be configured to get stored in Remote BLOB storages)

Types of Drives

Following are the types of drives we usually encounter.

PATA, SATA (Parallel/Serial Advanced Technology Attachment)

They are magnetic spinning drives with speed around 7200 rpm (rotation per minute).  The Parallel/Serial attributes the connector mechanism.  Usually SATA drives are faster than PATA drives.


SCSI (Small Computer System Interface)

They have higher spinning speed than the PATA/SATA alternative.  SCSI spins around 15000 rpm, but requires additional Motherboard Controllers leading to extra cost.

image    image

SSD (Solid State Drive)

SSDs use semi-conductors for storage, instead of magnetic components.  They are typically double in speed than the SATA/PATA alternative.  It is priced double than the normal hard disks.  They typically connects well with a SATA cables.


SSDs are gaining popularity due to their increased speed.

Another technology of interest is Fibre Channel (FC) Storage which was initially used in super computers, but now common in SAN (Storage Area Network)

Question: What is the recommended size of content database in normal scenarios?

200 GB

Question: What is the recommended size of content database in large-storage scenarios with high iops?

4 TB

(IOPS = Input/Output operations per second)



Fibre Channel

SharePoint Boundary Limits

Storage and SQL Server capacity planning and configuration

Posted in SharePoint, SharePoint 2010, SharePoint 2013 | Tagged: , , , | Leave a Comment »

Windows Azure – Storage Basics

Posted by Jean Paul on November 6, 2011

In this article we are discussing Storage Accounts in Windows Azure. We will start with the purpose first.

What is the purpose of Storage Accounts?

We know that in our traditional applications we need persistence like:

  • Storing Data in Database
  • Storing Information in Files

The persistence is needed for retrieving them later. As the Windows Azure is a different platform (Operating System) the storage mechanisms also differ.

Types of Storage in Windows Azure

There are mainly three types of storage:

  • Local Storage
  • Windows Azure Storage
  • SQL Azure Database Storage

Local Storage

  • Similar to normal file system storage
  • Faster way of storing data
  • Used for Temporary purposes and data is removed on instance restart
  • Multiple application access is restricted
  • No price involved

Windows Azure Storage

  • Durable Storage service
  • Multiple application access is possible
  • Pricing involved
  • 3 Types of storage: Blobs, Tables and Queues

Sql Azure Database Storage

  • RDBMS (Relational Database Management System)
  • Sql Server on the Cloud
  • Access data using ADO.NET or ODBC technologies
  • Pricing involved

The following image summarizes the types of storage.


Each storage example will be provided in the further articles.

More Information

More information on the pricing and features can be found in link

Posted in Azure | Tagged: , , , | Leave a Comment »

Staging and Production Servers

Posted by Jean Paul on November 6, 2011

Staging and Production Servers

In the previous article we have found how to deploy a new build to staging in Windows Azure. Now we need to move the staging build to production. Before that we are going to discuss the importance of staging and production servers.

Staging Environment

Staging environment will be having a configuration similar to the production environment. Before an application is released to production (where real users will be using), the application is test deployed to the staging environment. This gives us a chance to find potential bugs, security problems, configuration issues etc. It will save the team from entering into serious problems.

Production Environment

Production Environment will be the actual environment which the real users will be using. A build which was tested perfect in the staging environment is moved to the production environment.

The series of operation and the servers involved will be as following for a typical deployment. Typically, there will be a development machine where the application is created, deployed to a testing machine for the tester to find any bugs, deployed to staging and on successful validation deployed to Production server.



To summarize, we can say there are multiple machines involved in the development to deployment process.

  • Development Machine
  • Testing Machine
  • Staging Server
  • Production Server

Posted in Azure | Tagged: , , | Leave a Comment »