Database Reference
In-Depth Information
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 may prove
complex. For instance, the existing data platform is hosted with high availability components
such as failover clustering, database mirroring, and replication. Start to plan by analyzing
upgrade requirements, including reviewing upgrade strategies, understanding SQL Server
2008 R2 hardware and software requirements, and discovering any blocking problems
caused by backward-compatibility issues.
This recipe introduces you to the methods that need to be followed when you design an SQL
Server upgrade process. It will also present the best practices scenario for pre-upgrade,
during the upgrade, and post-upgrade tasks that are involved within the upgrade of current
SQL Server instance to SQL Server 2008 R2 version.
Getting Ready
The upgrade is not restricted to databases. It is important for the upgrade project to consider
the various tools, components, and services of SQL Server 2008 R2 and non-database
components, such as:
F
SQL Server Management Studio (SSMS)
F
Business Intelligence Development Studio (BIDS)
F
SQL Server Reporting Services (SSRS)
F
SQL Server Analysis Services (SSAS)
F
Data Mining
F
Linked Server configuration
F
Log Shipping servers
F
Database Mirroring pair
F
SQL Server Replication
F
SQL Server Agent jobs
F
DTS Packages
F
SQL Server Integration Services (SSIS)
F
Microsoft Desktop Engine (MSDE) or SQL Server Express edition
Further to the list of tools, components, and services, you need to include technical issues
(if any) and decisions that are involved in an upgrade to SQL Server 2008 R2, in addition to
recommendations for planning and deploying an upgrade. The upgrade processes include
upgrade strategies (pre/during/post), test, and rollback considerations and upgrade tools.
Search WWH ::
Custom Search