37
SQL Server 2012 Upgrade Technical Guide
server, and you can execute it from the Command Prompt window by using a
configuration filename as an input parameter.
Note: You can run the SQL Server 2012 Upgrade Advisor only against instances of
SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. You cannot run it
against instances of SQL Server 2000 or SQL Server 7.0.
Upgrade Advisor is a separate download. The most recent downloadable version is
available as part of the
Microsoft SQL Server 2012 Feature Pack
(http://www.microsoft.com/en-us/download/details.aspx?id=29065). You can find more
information about this valuable tool in
Use Upgrade Advisor to Prepare for Upgrades
(http://msdn.microsoft.com/en-us/library/ms144256(v=sql.110).aspx).
Best Practices Analyzer for SQL Server 2005, SQL Server 2008, and SQL Server
2008 R2
Before you install SQL Server 2012, you should also run the SQL Server Best Practices
Analyzer (BPA) against your current legacy instances of SQL Server. If bad or
questionable practices exist, you could address them before the upgrade, moving the
fixes through test and into production. Using best practices on the legacy SQL Server
systems first will help ensure a smoother upgrade, but that is not always possible. You
might have to change some practices during the upgrade process instead.
You can download the SQL Server 2005 version of BPA at the
SQL Server 2005 Best
Practices Analyzer (August 2008)
(http://www.microsoft.com/en-
us/download/details.aspx?displaylang=en&id=23864) download page.
You can download the SQL Server 2008 R2 BPA at the
SQL Server 2008 R2 Best
Practices Analyzer
(http://www.microsoft.com/en-us/download/details.aspx?id=15289)
download page. Use this for both SQL Server 2008 and SQL Server 2008 R2.
After you have upgraded, be sure to run the
SQL Server 2012 Best Practices Analyzer
(http://www.microsoft.com/en-us/download/details.aspx?id=29302). See also "Post-
Upgrade Tasks" in this chapter.
SQL Server 2012 Setup: System Configuration Checker
An in-place upgrade uses SQL Server 2012 Setup to directly upgrade SQL Server
2005/2008/2008 R2. The SQL Server 2012 Setup program installs prerequisites such as
the .NET Framework and PowerShell 2.0. It also scans the destination computer for
minimum hardware and software requirements, in addition to a compatible SQL Server
38
SQL Server 2012 Upgrade Technical Guide
edition upgrade path for an in-place upgrade. To do this, the SQL Server 2012 Setup
program contains a utility named the System Configuration Checker (SCC) that
performs a scan of the computer in preparation for an installation. For more
information, see
Check Parameters for the System Configuration Checker
(http://technet.microsoft.com/en-us/library/ms143753(SQL.110).aspx) in SQL Server
2012 Books Online.
The Setup SCC looks for conditions that will prevent a successful SQL Server installation
or upgrade. These checks occur before Setup starts the SQL Server 2012 Installation
Wizard and report any issues that would block an installation along with advice about
how to address the blocking issues. The Setup SCC uses rules from the following
categories; for more information about any of these categories, see the related link
from SQL Server 2012 Books Online:
Installation Rules
(http://technet.microsoft.com/en-us/library/cc646015(SQL.110).aspx)
Upgrade Rules Check
(http://technet.microsoft.com/en-us/library/cc281843(SQL.110).aspx)
Edition Upgrade Rules
(http://technet.microsoft.com/en-us/library/cc645998(SQL.110).aspx)
Uninstallation Rules
(http://technet.microsoft.com/en-us/library/cc645979(SQL.110).aspx)
The common, relevant rules—across all four categories—for an in-place upgrade and a
side-by-side upgrade, are as follows; failing any of these rules will result in a blocking
issue that could prevent an in-place upgrade:
The destination computer must be connected to the Internet while the .NET
Framework security check validates a certificate.
The destination computer cannot be a domain controller.
The SQL Server registry keys must be consistent.
The CPU architecture of the installation program must match the CPU
architecture of features intended for upgrading.
If the computer is clustered, the cluster service must be online.
Windows PowerShell 2.0 must be installed. (Setup will do this automatically
when it installs prerequisites.)
39
SQL Server 2012 Upgrade Technical Guide
SQL Server Setup must be supported on this operating system platform.
SCC checks whether a pending computer restart is required.
The existing performance counter registry hive must be consistent.
SCC checks that neither SQL Server 7.0 nor SQL Server 7.0 OLAP Services is
installed on the server. SQL Server 2012 is not supported on the same server
with SQL Server 7.0.
Here are some additional checks that SCC performs to determine whether the SQL
Server editions in an in-place upgrade path are valid:
Checks the system databases for features that are not supported in the SQL
Server edition to which you are upgrading.
Checks all user databases for features that are not supported by the SQL Server
edition.
Checks whether the SQL Server service can be restarted.
Checks that the SQL Server service is not set to Disabled.
Checks whether the selected instance of SQL Server meets the upgrade matrix
requirements (see "Allowable Upgrade Paths" in this section).
Checks whether SSAS is being upgraded to a valid edition.
Checks whether the edition of the selected instance of SQL Server is supported
in this scenario (see "Allowable Upgrade Paths" in this section as well as Chapter
4, "High Availability," later in this guide).
For more information about SQL Server 2012 Setup, see "SQL Server 2012 Setup" later
in this chapter.
Upgrade Assistant for SQL Server 2012 (UAFS)
The Upgrade Assistant for SQL Server 2012 (UAFS) is an external tool that lets you
determine in a test environment how an application currently running on SQL Server
2005, 2008, or 2008 R2 will run on SQL Server 2012. This tool uses the SQL Server 2012
Management Tools Distributed Replay (DReplay) utility, together with baseline and
trace replays in a test environment, to help identify compatibility issues.
The requirements for using the Upgrade Assistant are as follows:
Four servers are needed while doing replays.
Dostları ilə paylaş: |