Tip #89: File Import performance

Rate this item
(0 votes)
Migrating file shares to SharePoint 2010 requires a lot of activities around Information Architecture to design the taxonomy according the business needs and provide rich content usability, but apart of this a large portion of file migration engagement takes the actual migration process.

Migrating files to SharePoint is very time consuming process, due to the nature of SharePoint to store all content in Content Database. Therefore, all files that are published to SharePoint should be saved to SQL Server and performance of database is important.

There are several options how to migrate files to SharePoint:
  1. Metalogix File Migration imports 1-4GB per hour.
    Benefits - bulk import and migrating metadata.
    Constrains - slow process and tool price depends on the volume of migrating content (per GB)
  2. WebDav - 6-12 GB per hour.
    Benefits - very quick on small files (100Mb for 30secs); can copy files via XCOPY; drag-n-drop support;
    Constrains - slow on large files (500Mb for 10 minutes); not reliable on 1GB+ files
  3. RPC (depricated in SharePoint 2010)
  4. Copy Service - fast and reliable
    Summary:

    Copy Service

    WebDav

    RPC

    Metalogix

    100Mb

    00:01:20

    00:01:08

    n/a

    n/a

    1Gb

    00:04:34

    Fails all time

    n/a

    15mins – 1h

    Issue

    Can’t create folders

    Can’t send metadata with the content (need additional update call)

    IIS 7.5 doesn't support FPSE, can't test it

    Price per GB


    PS: I used the following code to test performance http://vspug.com/smc750/2009/05/19/uploading-content-into-sharepoint-let-me-count-the-ways/

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.