40
SQL Server 2012 Upgrade Technical Guide
Production Server: Contains the databases that will be migrated and the activity
that will be replayed.
Baseline Server: Has the same version of SQL Server as the Production Server
with the databases to be migrated on it. It is isolated in order to retrieve baseline
information without the effect of other applications or server activity. The
Upgrade Assistant for SQL Server 2012 will run its replay against this server,
resulting in the baseline trace file.
Test Server: This server has the new SQL Server 2012 instance.
If testing an in-place upgrade, this will be the baseline server after the SQL
Server 2012 upgrade has been applied.
If testing a side-by-side upgrade, this should be a separate server.
Report Server: This server with SQL Server 2012 Distribute Replay is used to save
trace file comparison results.
The Upgrade Assistant for SQL Server 2012 contains step-by-step instructions on
how to configure the Distributed Replay utility.
Windows Server 2003 R2, Windows Vista, or Windows XP SP2 or later versions
SQL Server 2000 SP4 or later versions or SQL Server 2005 SP2 or later versions
Microsoft .NET Framework 2.0 SP1 or later versions
Using the reports on the Report Server, compare the results of the baseline test
workload on SQL Server 2012 against the original baseline. If there are any material
differences between the two results, work to resolve them in advance of the production
upgrade.
For more information and download instructions, see
Upgrade Assistant for SQL Server
2012 (UAFS)
(http://www.scalabilityexperts.com/tools/downloads.html) on the
Scalability Experts Tools Downloads page.
SQL Server Profiler
SQL Server Profiler can record a running workload and then replay that same activity
from a given SQL Server instance, making it a valuable tool for preparing an upgrade.
Profiler is useful for simulating an upgrade to determine performance and correct
behavior. For example, you can use SQL Server 2012 Profiler to trace database activity
on a SQL Server 2005/2008/2008 R2 instance under load and save the trace. You can
then restore the legacy SQL Server database to two instances on equivalent hardware:
41
SQL Server 2012 Upgrade Technical Guide
an instance of the legacy SQL Server and an instance of SQL Server 2012. Run the
replay on each (but at different times if on the same server). While you are running the
replay, also run a Profiler trace on each run, capturing for errors and query durations.
By comparing the results, you can determine whether the upgrade behaves correctly
(without error) and performs well.
Note: When using Profiler make sure that the trace file contains a truly
representative load against the server, one that contains the full range of all queries
that the application will submit to the database. With a full range of queries and
sufficient load, testing can add confidence to the upgrade plan.
For more information about how to use Profiler for replay, see
Replaying Traces
(http://technet.microsoft.com/en-us/library/ms190995(SQL.110).aspx) in SQL Server
2012 Books Online.
System Monitor—SQL Server: Deprecated Features Object
You can use the SQL Server 2012 System Monitor (Perfmon) counter called
SQLServer:Deprecated Features to monitor whether your application is submitting
commands to the SQL Server 2012 Database Engine that are scheduled for removal
from SQL Server in future releases. You should remove such deprecated commands
from SQL Server 2012 applications after they are detected. You can use this counter to
help plan modifications to your application code so that when you upgrade to the next
version of SQL Server after SQL Server 2012, the upgrade process will go more
smoothly. Select which kind of feature to monitor by using the Instance selection box
for the counter. System Monitor records the total number of times the deprecated
feature was encountered since SQL Server 2012 was last started. For more information
about how to use this tool, see
SQL Server, Deprecated Features Object
(http://msdn.microsoft.com/en-us/library/bb510662(v=sql.110).aspx) in SQL Server
2012 Books Online.
Analysis Services Migration Wizard
The Analysis Services Migration Wizard can help with a side-by-side upgrade of SSAS.
For information about this tool, see Chapter 16, "Analysis Services."
Notification Services
You cannot perform an in-place upgrade of SQL Server Notification Services because it
is not installed by SQL Server 2012. You must use the SQL Server 2008 R2 Notification
Services backward compatibility add-in; see Chapter 9 in
SQL Server 2008 R2 Upgrade
42
SQL Server 2012 Upgrade Technical Guide
Technical Reference Guide
(http://download.microsoft.com/download/3/0/D/30DB8D46-8ACF-442A-99A2-
0F4CE74AE14D/SQL_Server_2008_R2_Upgrade_Technical_Reference_Guide.docx).
SQL Server 2012 Setup
When planning an upgrade to SQL Server 2012, you first have to make sure that the
target servers meet the necessary hardware and software requirements for SQL Server
2012 Setup to be completed.
Note: If your production instance of SQL Server 2005/2008/2008 R2 is installed on
Windows Server 2003, you must upgrade to a new server by using a side-by-side
upgrade. SQL Server 2012 is not supported on Windows Server 2003 and an in-
place upgrade is not possible.
Setup Requirements for an In-Place Upgrade
SQL Server 2012 Setup has important version-level requirements for upgrading
instances of SQL Server 2005, 2008, and 2008 R2 in-place. The basic requirements are
as follows:
SQL Server 2005: SP4 is required.
SQL Server 2008: SP2 is required.
SQL Server 2008 R2: SP1 is required.
For an in-place upgrade, the target SQL Server 2012 server and the legacy instance of
SQL Server 2005/2008/2008 R2 must satisfy some additional requirements for SQL
Server 2008 R2:
Cross-version instances of SQL Server 2012 are not supported. Version numbers
of the Database Engine, Analysis Services, and Reporting Services components
must be the same throughout an instance of SQL Server 2012. Therefore, you
must upgrade all these components together during an in-place upgrade.
Make sure that sufficient disk space is available for SQL Server 2012 Setup. Disk
space requirements vary based on the components selected to upgrade. For disk
space amounts, see the "Hard Disk Space Requirements (32-Bit and 64-Bit)"
section in the Hardware and Software Requirements for Installing SQL Server
2012 topic (http://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx)
in SQL Server 2012 Books Online.
Dostları ilə paylaş: |