43
SQL Server 2012 Upgrade Technical Guide
Before upgrading SQL Server, enable Windows Authentication for SQL Server
Agent and verify the default configuration (that the SQL Server Agent service
account is a member of the SQL Server sysadmin group).
Before upgrading from one edition of SQL Server 2012 to another, verify that the
functionality currently being used is supported in the edition to which you are
upgrading. For more information, see the section for specific components in
Planning a SQL Server Installation
(http://msdn.microsoft.com/en-
us/library/bb500442(v=sql.110).aspx) in SQL Server 2012 Books Online.
Cross-platform in-place upgrades from 32-bit to 64-bit (x86 to x64) versions and
vice versa are not supported.
Make sure that you are running a supported version of the Windows operating
system.
The in-place upgrade will be blocked if:
o
The server has a pending restart.
o
The Windows Installer service is not running.
o
Windows System Monitor Performance Counters are corrupted.
To upgrade an instance of SQL Server to a SQL Server failover cluster, the
instance being upgraded must be a failover cluster (or it must be upgraded to a
failover cluster first). In other words, to upgrade a standalone instance of SQL
Server to a SQL Server failover cluster, install a new SQL Server failover cluster,
and then move user databases from the standalone instance by using the Copy
Database Wizard. (See Chapter 4, "High Availability," for more information.)
Note: When the in-place upgrade process is running, avoid making any changes
to the legacy SQL Server 2005/2008/2008 R2 system.
For more information, see the "Unsupported Scenarios" section in the
Supported
Version and Edition Upgrades
topic (http://msdn.microsoft.com/en-
us/library/ms143393(v=sql.110).aspx) in SQL Server 2012 Books Online.
SQL Server Prerequisites Installed by Setup
The SQL Server 2012 Installation Wizard installs the following prerequisites (if they are
not already present on the computer):
.NET Framework 3.5 SP1
44
SQL Server 2012 Upgrade Technical Guide
SQL Server Native Client
SQL Server support files
To reduce the time that is required for the upgrade process, install the .NET Framework
3.5 SP1 components (you must have SP1 or a later version) and SQL Server 2012 Native
Client beforehand on the server that will be upgraded. Then, include the same
components on the baseline image of the test server. If the production system cannot
be disturbed in any way before the scheduled downtime for the upgrade process, the
SQL Server 2012 Setup program will automatically install the prerequisites as part of
the upgrade process. However, this increases the time that is required for the upgrade.
PowerShell 2.0 is required by SQL Server 2012. If the target SQL Server is running
Windows Server 2008 SP2, install and enable PowerShell 2.0. If it is running Windows
Server 2008 R2 SP1, enable PowerShell 2.0. SQL Server 2012 Setup also installs the SQL
Server PowerShell snap-ins.
Note: The sqlps.exe command prompt utility for running SQL Server 2008 R2
PowerShell snap-ins has been deprecated.
Instance ID and Paths
Whether you are performing an in-place upgrade or a side-by-side upgrade, SQL
Server Setup will ask for an Instance ID. The Instance ID is a unique identifier specified
during the upgrade (or install) to identify that specific SQL Server 2012 installation. The
Instance ID behaves similarly to an instance name, but it has some additional features.
Default instances of SQL Server always have a default value of MSSQLSERVER. In
addition, the Instance ID is recorded in SQL Server 2012 program files, which are
located by default at X:\Program Files\Microsoft SQL Server\MSSQL11.InstanceID,
where X is your system drive, such as drive C.
For a named instance, choose an Instance ID that makes sense; do not necessarily
accept default values. This is especially true for failover clustering implementations,
where instances are not "local" and will have a presence on each node. (For more
information about clustering, see Chapter 4, "High Availability.")
Minimum Hardware and Software Requirements for SQL Server 2012
In this section, we describe the minimum hardware and software requirements for
running SQL Server 2012. For detailed information about the minimum hardware and
software requirements for all editions of SQL Server 2012, see
Hardware and Software
Requirements for Installing SQL Server 2012
(http://msdn.microsoft.com/en-
45
SQL Server 2012 Upgrade Technical Guide
us/library/ms143506(v=sql.110).aspx) in SQL Server 2012 Books Online. The following
subsections are pasted for the reader’s convenience from information found in this link.
The link might contain more recent information than what is in this topic.
The following minimum hardware and software requirements apply to all SQL Server
2012 editions:
SQL Server 2012 Setup will install .NET 4.0, the SQL Server Native Client, and the
required SQL Server 2012 Setup support files.
.NET requirements:
o
If you are installing SQL Server 2012 on a Windows Vista SP2 or Windows
Server 2008 SP2 server, you must download and install .NET Framework
3.5.
o
On Windows 7 and Windows Server 2008 R2 SP1, you must enable .NET
Framework 3.5.
o
The .NET 4.0 is a requirement of SQL Server 2012, and SQL Server 2012
Setup will install it during the feature installation step.
o
If you are installing SQL Server 2012 Express on Windows 2008 R1 SP1
Core, you must first install .NET 4.0.
Windows PowerShell 2.0 is not installed by SQL Server 2012 but it is required.
You can download and install Windows PowerShell 2.0 from the
Windows
Management Framework
site (http://support.microsoft.com/kb/968929).
Processor, Memory, and Operating System Memory Requirements
The processor and memory minimum requirements are the same for all the SQL Server 2012
editions. The page at
Hardware and Software Requirements for Installing SQL Server 2012
(http://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx) specifies those
requirements.
The operating system minimum requirements vary based on the SQL Server 2012 edition you
select. The following links will take you to the appropriate sections for the server-based
editions of SQL Server 2012:
Principal Editions of SQL Server 2012
(http://msdn.microsoft.com/en-
us/library/ms143506.aspx#top_principal)
SQL Server Enterprise (64-bit)
SQL Server Business Intelligence (64-bit)
Dostları ilə paylaş: |