The objective of this document is to present the high level plan for implementation, migration and Upgradation of SQL Server Database.

Transcription

1 Objective of the Document The objective of this document is to present the high level plan for implementation, migration and Upgradation of SQL Server Database. Physical to Virtual Database Migration 1.1 Migrating Existing Database to VMware There are two main approaches when migrating an existing database from physical servers to virtual servers. The first approach is to use a conversion tool to migrate the database as is. The second approach is to perform a new installation of the database software in the virtual environment, and migrate the data from the legacy physical server. 2.2 Physical to-virtual Conversion VMware VCenter Converter can be used to convert existing physical database servers to virtual machines through a process commonly referred to as physical-to-virtual (P2V) conversion. VMware VCenter Converter simplifies the P2V conversion through intuitive wizard-driven automation. To maintain consistency of the database, it is recommended that you stop the database services (but leave the OS running) during hot cloning of the physical database server. P2V conversion through VCenter Converter accomplishes a one-to-one mapping between the physical server and the virtual server. 2.3 New Database Installation Existing physical databases can be migrated to a virtual machine by performing a new Installation of the database software on the virtual machine, and then migrating the data to The virtual machine from the source physical server with the help of this approach we will upgrade the customer database version along with migration. SQL Server 2005 server which is running on Physical server and that we are virtualizing, we can choose to upgrade the SQL Server 2005 instance by installing a new SQL Server 2008 R2 instance on the virtual machine, and then restoring a backup copy of the SQL Server 2005 database onto the SQL Server 2008 R2 instance. Even If Raw Disk Mapping (RDM) is used in the database virtual machine, database files can be detached from the physical database, and attached to the database on the virtual machine. The entire backup/copy/restore process is eliminated, so cutting over from the physical server to the virtual server could be accomplished in seconds. This is especially useful for migrating databases with large on disk footprints and/or for mission critical databases that demand high uptime. For mission critical databases that demand high uptime this migration approach also enables the use of native database replication features such as SQL Server database mirroring, and log shipping to perform zero downtime P2V migration. With database replication features such as SQL Server database mirroring, the physical database and the virtual database can run side-byside as database mirroring partners. While data is being replicated onto the virtual database, the physical database continues to accept user requests. After the data is completely synchronized on the virtual machine, you can perform a manual failover to the virtual machine and remove the physical server from the mirroring partnership.

2 2. SQL Server up gradation to SQL Server Upgrade Strategies An upgrade is any kind of transition from SQL Server 2005, 2008, or 2008 R2 to SQL Server There are two fundamental strategies for upgrading, with two main variations in the second strategy: 1. In-place upgrade: Using the SQL Server 2012 Setup program to directly upgrade an instance of SQL Server 2005, 2008, or 2008 R2. The older instance of SQL Server is replaced. 2. Side-by-side upgrade: Using steps to move all or some data from an instance of SQL Server 2005, 2008, or 2008 R2 to a separate instance of SQL Server There are two main variations of the side-by-side upgrade strategy: In-Place Upgrade By using an in-place upgrade strategy, the SQL Server 2012 Setup program directly replaces an instance of SQL Server 2005, 2008, or 2008 R2 with a new instance of SQL Server An inplace upgrade requires that the old and new instances of SQL Server be on the same x64 platform. This kind of upgrade is called "in-place" because the upgraded instance of SQL Server 2005/2008/2008 R2 is actually replaced by the new instance of SQL Server You do not have to copy database-related data from the older instance to SQL Server 2012 because the old data files are automatically converted to the new format. When the process is complete, the old instance of SQL Server 2005/2008/2008 R2 is removed from the server, with only the backups that you retained being able to restore it to its previous state. Below figure shows the In-Place up gradation Note: Incase if we have to upgrade one database from a legacy instance of SQL Server and not upgrade the other databases on the server, we have to use the side-by-side upgrade method instead of the in-place method.

3 Side By Side Up gradation Run the new instance of SQL Server 2008 R2 alongside the legacy instance of SQL Server 2005/2008/2008 R2. Typically, after the upgraded instance is accepted and moved into production, you can remove the older instance. Side-by-side upgrade is to a separate instance on the same server or to a new instance on another server, data must be transferred in what is mostly a manual process. The result is two instances, legacy and new, that can run side by side. As just noted, the key point in a side-by-side upgrade is that you must manually transfer data files and other supporting objects from the older instance of SQL Server to the instance of SQL Server The SQL Server 2012 Setup program will not perform this task. Below figure explain the Side By Side Up gradation. Note: It is not possible to upgrade from SQL Server 2000 Express edition to SQL Server 2012.To achieve the up gradation you have to upgrade the database from Express edition to SQL server 2000 Ent. Or Stnd. Edition than SQL Server 2005 Enterprise Edition with Service Pack 4 than SL Server 2008 or 2008 R2 with Service Pack 2 once the entire procedures done than only we can upgrade the database to SQL Server 2012.

4 Limitations There are several limitations to be aware of before upgrading to SQL Server The most important limitations are: Windows Server 2003 isn't a supported OS. If your instance of SQL Server is running on a Windows Server 2003 system, you must upgrade the OS before upgrading to SQL Server A cross-platform upgrade isn't supported. You can't upgrade a 32-bit version of SQL Server to a 64-bit version. You can't add new features as a part of the upgrade process. However, you can add new features after the upgrade. The Windows Installer service must be running. Microsoft.NET Framework 3.5 SP1 and.net Framework 4.0 are required. Windows PowerShell 2.0 or later is required if you're upgrading the database engine. IIS 7.0 or later is required for the Microsoft Management Console (MMC), SQL Server Data Tools, Report Designer in SQL Server Reporting Services (SSRS), and HTML help.

5 Effort Estimate EFFORT ESTIMATION Manpower Classification Helper man-days L1 Man L2 Man L3 Man L4 Man Activity List Remarks Implementation at DC Database configuration understanding Database backup before starting activity New Database implementation P2V migration Database Up gradation Database consolidation on shared database instance. All database consistency check and statistics and Index update Status Database handover to application team and testing Database documentation Implementation at DR Documentation Installation of Database Replication configuration between DC to DR and Failover Testing Database handover and Testing