Tuesday 26 February 2013

Pros and Cons of Moss 2007 to SharePoint 2010 migration Scenarios

SharePoint resources can offer high value at reasonable cost in any organization deploying SharePoint platform. With the improved features of this technology, organizations in India are showing interest to use it for content, people, and process management. Overall information systems efficiency and quicker ROI have every reason to get increased for using this Microsoft web application platform. Many IT firms deploy SharePoint resources to help organizations get cost-effective resources. While Indian IT companies are working on projects outsourced by offshore clients, many native firms are serving different companies in the country as like as working on projects outsourced among similar groups.

Deployment of SharePoint Resources
Expert SharePoint developers must be proficient in SharePoint Deployments of resources like MOSS 2007, SharePoint 2010, .NET development, Active Directory, SharePoint Designer, and SharePoint Foundation Server 2010. Different application services in use in reputed IT firms include training, migration, integration, deployment, development, and customization of SharePoint. Application architecture and design and post-implementation of SharePoint services are beneficial in managing various business processes in any midsize or large organization.

Microsoft SharePoint Server 2010 offers flexibility of rich deployment. This allows firms to decide the appropriate deployment situations suitable to their business objectives and requirements. The Windows Azure Virtual Machines are managed in the cloud with the offering reliable, complete, and available infrastructure that can support di8fferent kinds of database workloads and on-demand application. SharePoint deployments and Microsoft SQL Server are good examples in this regard.

The Migration Process
One can cite two probable scenarios for MOSS 2007 to SharePoint 2010 migration. It is better to begin from a farm operating MOSS 2007 SP1 on 32-bit windows server OS.

Following are the predicted scenarios:

• Database attach with Read-only databases
• In-place upgrade with detected databases on a separate farm

Migrating Step-by-Step

While migrating, ‘Preupgradecheck’ must be run first in MOSS 2007 server and analyzing and fixing issues. Backing up of content databases from MOSS 2007 is the second step. Thirdly, it is necessary to restore this backup to SQL Server of SharePoint 2010. Web application is created after that. In the next sequence, MOSS 2007 content databases have to be attached to SharePoint 2010. The final step in the migration process is to post migration fixes.

Pros and Cons of Migration Scenarios

The 2-step migration scenarios mentioned above are safer, cleaner, more flexible, and of more service availability and faster upgrade time. That the steps need more work and are costlier are acceptable considering the complexity of the entire migration process.

No comments:

Post a Comment