Getting Started with SQL Server 2008 R2 - Microsoft SQL Server 2008 R2 Administration - page 12

For SQL Server 2008 and SQL Server 2008 R2 version download
from http://www.microsoft.com/downloads/en/details.
aspx?FamilyID=0fd439d7-4bff-4df7-a5 2f-9a1be8725591 .

2. To install SQL Server 2008 R2 BPA tool the following tools are required:

PowerShell V2.0: review the requirements and d ownload it from
http://support.microso ft.com/kb/968929 .
Microsoft Baseline Configuration Analyzer (MBCA) V2.0: review the
requirements and download from http://www.microsoft.com/
downloads/en/details.aspx?displaylang=en&FamilyID=1b
6e9026-f505-403e-84c3-a5dea704ec67 .

3. Start the installation process for BPA tool by double-clicking on the downloaded file.
4. Upgrade strategies include two fundamental methods, they are: 'side-by-side' and 'in-

place'. It's worth mentioning about additional conventional methods of upgrade, such
as using Copy Database Wizard and manual Schema rebuild method with scripts.
Using the side-by-side upgrade requires the user to move all or some data
from an instance of SQL server 2000, or SQL Server 2005, or SQL Server
2008 to a separate instance of SQL Server 2008 R2. The variations in this
strategy include, one-server—the new instance exists on the same server
as target instance); and two-servers—the new instance exists on a different
server than the target instance.
Using the in-place upgrade will involve a direct upgrade of the previous
version of SQL Server to SQL Server 2008 R2, where the older instance
is replaced.
Using Copy Database Wizard to upgrade an SQL Server 2000 or SLQ Server
2005 database, offers the advantage for the database to be available
immediately, which is then upgraded automatically.

Using the Schema rebuild method with scripts is a manual operation, which
requires individual script files to create database, tables, logins, users,
and scheduled jobs. Additionally, these external components also require
scripting, such as SSIS packages, Linked Server information, and database
maintenance plans.

5. Documentation is the key to a successful upgrade. Everyone should work as
part of a team. The planning process will begin with a document that stands as
a communication to involve all the stakeholders and teams to complete the data
platform upgrade process.
6. In case of any specific requirement from Business teams within the upgrade process,
that information must be documented in an Upgrade document along with their
contact information.