Database Reference
In-Depth Information
7. Using the documentation acts as a base to execute the upgrade during the
deployment phase. The plan should be as detailed as possible, and you should store
the resulting document or documents by using some form of change control, such as
a source control system. In the rest of this section, we will detail these steps.
8. Finally, within that planning documentation, include the upgrade requirements in
addition to the rationale for choosing an upgrade strategy (refer step 3) for each
instance or class of instances. Use the rest of the plan to detail remaining issues.
9. Detail the steps required for taking the systems offline for a period of time and
bringing them back online.
10. Upgrade the Advisor tool:
Upgrade Advisor is available in the
\X86
(or
x64
,
ia64)\redist\Upgrade
Advisor
folder of the SQL Server installation media.
The tool is also available from Microsoft SQL Server 2008 R2
aae0c5c83
d52&displaylang=en
.
Within this feature pack page choose the appropriate file that suits to the environment,
X86
,
X64,
or
IA64
.
11. Run the SQL Server 2008 Upgrade Advisor to determine potential blocking issues:
Deprecated features
Discontinued features
Breaking changes
Behavior changes
It analyzes objects and code within legacy instances to produce reports that detail upgrade
issues, if there are any, organized by SQL Server component.
The resulting reports show detected issues and provide guidance about how to fix the issues,
or work around them. The reports are stored on disk, and we can review them by using
Upgrade Advisor or export them to Microsoft Excel for further analysis.
In addition to analyzing data and database objects, Upgrade Advisor can analyze Transact-
SQL scripts and SQL Server Profiler/SQL Trace traces. Upgrade Advisor examines SQL code for
syntax that is no longer valid in SQL Server 2008 R2.
Search WWH ::
Custom Search