Even before Microsoft released SQL Server 2005 Service Pack 1, the wheels were turning for many DBAs to begin migrating to SQL Server 2005.
In an earlier step-by-step guide on planning your migration, I outlined how to move from SQL Server 2000 to 2005. You should consider all of the many options available based on your unique environment, and take into account that the decision is situational and the migration process may not be the same for every upgrade.
I think a common scenario will be the migration of a database from a SQL Server 2000 server to a SQL Server 2005 server. As it pertains to upgrading a single database and its objects, I think the Copy Database Wizard will be a popular option for small to mid-sized databases because it can include dependent objects (logins, DTS packages, jobs, etc.). As such, this guide will outline steps to migrate from SQL Server 2000 to 2005 by using the Copy Database Wizard method. At a high level, this tool creates one or more SQL Server Integration Services (SSIS) packages to complete the migrati...
To continue reading for free, register below or login
To read more you must become a member of SearchSQLServer.com
');
// -->

on either by detaching and attaching the database or using SQL Management Objects (SMO) to move the data.
Note: For a webcast outlining the technical options with the pros and cons of each option, reference Weighing your SQL Server 2005 migration options.
ABOUT THE AUTHOR:
[IMAGE]Jeremy Kadlec
Jeremy Kadlec is the principal database engineer at Edgewood Solutions, a technology services company delivering professional services and product solutions for Microsoft SQL Server. He has authored numerous articles and delivers frequent presentations at regional SQL Server users groups and nationally at SQL PASS. Kadlec is the SearchSQLServer.com Performance Tuning expert. Ask him a question here.
Copyright 2006 TechTarget