Site sponsored by: Idera The gold standard of SQL Server performance monitoring & diagnostics.
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


Article Topics

All Articles
Performance Tuning
Audit
Business Intelligence
Clustering
Reporting Services
Developer
General DBA
ASP.NET / ADO.NET

Write for Us

Share you SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Claytons Data Mining (Part 2)
Backup System Databases Using Maintenance Plans
Overview of Maintenance Plans in SQL Server 2008
Monitoring Index Fragmentation

More     
 
Latest FAQ's

How to alter a User Defined Data Type?
How to unzip a File in SSIS?
How to view previous query plans?
ALTER TABLE SWITCH statement failed because the object '%.*ls' is not ...

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

articles >> general dba >> SQL Server Upgrade Recommendations and Best Practices ...

SQL Server Upgrade Recommendations and Best Practices Part 1: Upgrade Overview and Project Planning

By : Jeremy Kadlec
Jun 14, 2003

Page 4 / 5

Upgrade Project Phases

In order to properly address the SQL Server 2000 Upgrade, it is necessary to setup a project plan with the necessary components for your environment. Below outlines a set of recommendations for the upgrade project plan. Can be further broken down with dates and time frames

Upgrade Project Phases1

ID

Phase

Description

1

Requirements Analysis

  • Setup a comprehensive Project Plan with tasks granular enough to assign to a single individual on the project

  • Hold a Kick-Off Meeting to properly start the project

  • Determine Upgrade Date and Time with the associated Downtime

  • Determine the Upgrade Freeze and Thaw Dates for Testing Purposes

  • Setup Roles and Responsibilities in order to establish Project Accountability

  • Submit a Change Management Request to notify key players in the corporation

  • Determine SQL Server Hardware Needs via Capacity Planning (disks, memory, processors, etc.)

  • Sign-Off – Requirements Analysis

2

Design and Development

  • Build an Upgrade Checklist to determine time frames and proposed processes to complete the Upgrade

  • Test the Upgrade Checklist and verify the results

  • Communicate the process to the team especially in terms of configurations

  • Sign-Off – Upgrade Methodology

3

Functional, Integration, End User and Load Testing

  • Setup a Test Environment to include the necessary SQL, Middle Tier and Web Servers as well as a Client PC; these machines should be configured as closely as possible to the Production Environment to ensure project success

  • Implement a Load Testing Tool

  • Build Test Plans for Functional, Integration, End User and Load Testing

  • Complete Functional, Integration, End User and Load Testing

  • Manage the Testing Exceptions until Completion for the Upgrade

  • Determine if Front End or T-SQL code must be applied prior to or following the upgrade in order to determine the code roll-out coordination

  • Update previously submitted Change Management request based on Testing results

  • Sign-Off – Testing

4

Production Hardware Setup

  • Server Assembly as well as Windows and SQL Server 2000 Installation

  • Configure, setup and burn-in the new hardware

  • Sign-Off – Production Hardware

5

Upgrade

  • GO | NO GO Meeting

  • Execute the Upgrade Checklist

  • Sign-Off SQL Server 2000 Upgrade

  • Monitor SQL Server Performance

  • Sign-Off – SQL Server 2000 Upgrade

 

Part 2 – Critical Upgrade Decisions and Redundant Upgrade Architecture

In the coming weeks, the next article in the series will detail the Critical Upgrade Decisions related to ANSI NULLS, Quoted Identifiers, etc as well as a valuable Redundant Upgrade Architecture for the project. These decisions can make or break the upgrade and require fore thought at the inception of the project. Further, find out how to prevent management’s biggest fear during systems upgrades with a redundant architecture. Be sure to check it out.


<< Prev Page     Next Page>>    








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved