19
SQL Server 2012 Upgrade Technical Guide
SQL Server 212 introduces important new features in the mission critical area, most
notably with new AlwaysOn features, as well as the new PowerView application for
Analysis Services reporting. For more information about these and other new features,
see
SQL Server 2012 Editions
(http://www.microsoft.com/sqlserver/en/us/editions.aspx)
and download the
SQL Server 2012 Product Guide
(http://www.microsoft.com/en-
us/download/details.aspx?id=29418).
Upgrading SQL Server 2008 to SQL Server 2008 R2
SQL Server 2008 R2 is a minor revision for most SQL Server 2008 components, with the
exception of Reporting Services, failover clustering, and shared components such as the
SQL Server Management Tools.
SQL Server 2008 R2 Reporting Services is an important exception in that it
contains significant changes from SQL Server 2008. For details, see Chapter 16,
“Reporting Services,” in this document.
SQL Server 2008 failover clustering has some important considerations because
Windows Server 2008 R2 was released after SQL Server 2008, and SQL Server
2008 R2 takes advantage of new Windows Server 2008 R2 failover clustering
features. For information about these new features, see the failover clustering
sections of Chapter 4, “High Availability.”
Because SQL Server 2008 and SQL Server 2008 R2 instances share many of the
same components, running them together on the same server over a long
period of time has a number of implications:
o
You must update both the SQL Server 2008 and SQL Server 2008 R2
instances separately with service packs and cumulative updates.
o
Installing SQL Server 2008 R2 on the same server as SQL Server 2008 will
automatically upgrade the Management Tools to the SQL Server 2008 R2
version, amounting to an automatic in-place upgrade of the Management
Tools.
o
Uninstalling the SQL Server 2008 R2 instance will prompt you about
removing shared components. If you remove shared components
required by the SQL Server 2008 instance, you will be warned that doing
so may make the SQL Server 2008 instance unusable.
20
SQL Server 2012 Upgrade Technical Guide
Most components of SQL Server do not differ significantly from SQL Server 2008 to
SQL Server 2008 R2 and can be upgraded using either the in-place or side-by-side
strategies, as described in the next section and in the remaining chapters of this
document. For more information about SQL Server 2008 and SQL Server 2008 R2, see
Considerations for Side-by-Side Instances of SQL Server 2008 R2 and SQL Server 2008
(http://msdn.microsoft.com/en-us/library/ee210714.aspx) in SQL Server 2008 R2 Books
Online.
Preparing to Upgrade
To prepare for an upgrade, begin by collecting information about the effect of the
upgrade and the risks it might involve. When you identify the risks up front, you can
determine how to lessen and manage them throughout the upgrade process.
Upgrade scenarios will be as complex as your underlying applications and instances of
SQL Server. Some scenarios within your environment might be simple, other scenarios
complex. Start to plan by analyzing upgrade requirements, including reviewing upgrade
strategies, understanding SQL Server 2012 hardware and software requirements, and
discovering any blocking problems caused by backward-compatibility issues.
Upgrade Strategies
An upgrade is any kind of transition from SQL Server 2005, 2008, or 2008 R2 to SQL
Server 2012. There are two fundamental strategies for upgrading, with two main
variations in the second strategy:
In-place upgrade: Using the SQL Server 2012 Setup program to directly
upgrade an instance of SQL Server 2005, 2008, or 2008 R2. The older instance of
SQL Server is replaced.
Side-by-side upgrade: Using steps to move all or some data from an instance
of SQL Server 2005, 2008, or 2008 R2 to a separate instance of SQL Server 2012.
There are two main variations of the side-by-side upgrade strategy:
One server: The new instance exists on the same server as the target instance.
Two servers: The new instance exists on a different server than the target
instance.
In-Place Upgrade
By using an in-place upgrade strategy, the SQL Server 2012 Setup program directly
replaces an instance of SQL Server 2005, 2008, or 2008 R2 with a new instance of SQL
21
SQL Server 2012 Upgrade Technical Guide
Server 2012 on the same x86 or x64 platform. (An in-place upgrade requires that the
old and new instances of SQL Server be on the same x86 or x64 platform. See the note
in "Extended System Support (WOW64)" later in this chapter.) This kind of upgrade is
called "in-place" because the upgraded instance of SQL Server 2005/2008/2008 R2 is
actually replaced by the new instance of SQL Server 2012. You do not have to copy
database-related data from the older instance to SQL Server 2012 because the old data
files are automatically converted to the new format. When the process is complete, the
old instance of SQL Server 2005/2008/2008 R2 is removed from the server, with only
the backups that you retained being able to restore it to its previous state.
Note: If you want to upgrade just one database from a legacy instance of SQL
Server and not upgrade the other databases on the server, use the side-by-side
upgrade method instead of the in-place method.
Figure 1 shows the before and after states of an in-place upgrade.
Figure 1: In an in-place upgrade, SQL Server 2012 Setup replaces a legacy instance of
SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2
Note the following restrictions on an in-place upgrade:
SQL Server 2012 Setup requires that all SQL Server components be upgraded
together. Setup will detect all the components of the instance to be upgraded
and will require that they all be upgraded immediately. In other words, you
cannot upgrade only an instance of the SQL Server 2008 R2 Database Engine
without also upgrading the Analysis Services component.
Dostları ilə paylaş: |