Why you should build data externalization into your #SharePoint#migration plan #SP2013

SharePoint 2013 is coming! SharePoint 2013 is coming! And so it begins: thinking about when you want to migrate! Maybe you're still thinking about migrating to Sharepoint 2010!


During this delibration process, you should consider how the growth, and its expected growth, of your SharePoint environment will fit into the new version. Do you have room in SQL to scale? Do you have the budget to purchase more space? Do you have the SharePoint and SQL performance you want and how will new growth impact that performance?


These are all questions our customer Conexus Credit Union asked themselves as they were preparing for a migration of their member investment and loan documents (all 1.2 million of them) from a legacy data system into SharePoint. Their SQL DBA was concerned about ALL that data hitting SQL and affecting performance. So they found a way to use SharePoint without storing the documents in SQL and jeopardizing performance - Storage Maximizer for SharePoint!


Here are the results Conexus found by using Storage Maximizer for SharePoint to externalize their SharePoint data during the migration:


    • Enabled externalization of 1.2 million documents during migration to SharePoint, without slowing the migration
    • Improved SharePoint performance by reducing the burden on SQL Server
    • Enhanced customer satisfaction and employee productivity
    • Projected to deliver cost savings by enabling use of less-expensive, tiered storage
    • Increased SharePoint scalability
    • Delivered exceptional customer support

"Our staff regularly use SharePoint to access documents throughout the day while working with customers, so quick response time is important to the customer experience. By externalizing many of our documents, Storage Maximizer gives us the SharePoint performance we need," explained Joanne Klein, SharePoint Administrator at Conexus.