Chapter overview: Deploy a new farm, then migrate databases (Windows SharePoint Services)
Updated: December 1, 2006
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2007-12-13
If you are moving to new hardware, or redesigning and restructuring your deployment, you can choose to migrate your databases from the old version to the new version rather than directly upgrading them. When you perform a database migration, you perform an in-place upgrade on the databases, but you do not upgrade your server farm configuration data. Although this upgrade path has more manual steps than either an in-place or a gradual upgrade, it can be the best option if you have highly customized sites or custom Web services or applications.
|Before you begin the process, be sure you have performed the planning and pre-upgrade steps. For more information, see Chapter overview: Plan and prepare for upgrade and Chapter overview: Perform pre-upgrade steps (Windows SharePoint Services).|
Perform a database migration by using the following steps:
Create the environment for the new version. See Prepare the new Windows SharePoint Services 3.0 environment.
Back up or copy the databases, and then migrate the data.
If you have a server farm, see Migrate content databases.
If you have a stand-alone server, see Migrate content databases from WMSDE to Windows Internal Database.
After you have completed these steps, you can go on to the Perform post-upgrade steps (Windows SharePoint Services) chapter and perform the following steps:
Review the sites to be sure they upgraded properly. See Review upgraded sites (Windows SharePoint Services)
Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services). Because database migration is essentially an in-place upgrade for your content, you can use the same post-upgrade steps.
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable books for Windows SharePoint Services.