SQL Server is the engine that fuels many organizations and has empowered the organization to reach new business...
and IT goals. As such, migrations to SQL Server 2005 have far-reaching affects that were not necessarily the case with migrations to SQL Server 2000.
To truly support the enterprise, SQL Server is now used more than ever before. The following components should be considered when migrating to SQL Server 2005:
- Database Engine databases and objects
- Analysis Services databases and objects
- Reporting Services objects
- Extraction Transformation and Loading (ETL) code [i.e., Data Transformation Services (DTS) to SQL Server Integration Services (SSIS)]
- Notification Services
- External scripts
- Middle-tier and front-end applications
- Third-party tools
- New application development
Surveying your environment to determine SQL Server components as compared to "go forward" applications from a business perspective is important. It ensures that the technical plan is comprehensive and does not experience any false starts. Once you have a clear understanding of the SQL Server components that you will be migrating, then can you determine the best technical options.
Migrating to SQL Server 2005
Step 1: What to upgrade
Step 2: Upgrade prerequisites
Step 3: Migration options
Step 4: Additional considerations
ABOUT THE AUTHOR:
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. Jeremy is also SearchSQLServer.com's Performance Tuning expert.
More information from SearchSQLServer.com
- Tip: Reduce upgrade unknowns with SQL Server 2005 Upgrade Advisor
- Learning Guide: SQL Server 2005 Learning Guide
- Book Excerpts: SQL Server 2005 Management Studio