Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Moving MS Project instance from cluster

Author  Topic 

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2012-07-14 : 19:33:09
Hi,

We have one instance of Ms Project that have dbs on sql server 2008 cluster seperate instance. Our plan is to migrate this instance (dbs) from cluster to vm. We will cretae another instance (will install same sql server version and edition but this time on seperate server (vm) and will keep the same instance name).

I just need to know steps DBA will performs and if possible overall steps and any issue?

Thanks

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-07-15 : 00:35:09
It's the exact same steps as any migration. I always use database mirroring so that there's only a few seconds of downtime. Don't forget any objects that are external to the user database such as Agent jobs, logins, and SSIS packages.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2012-07-16 : 18:00:33
Thanks Tara for reply.

Here what I am planning:
1. Crate new SQL instance on VM.
2. script login on source and create them on vm.
3. Backup user databaes and restore them on VM.
4. check orphaned users.
5. Move jobs, SSIS packages etc.
6. Create db mirroring b/w databases on source and vm.
7. During outage failover databases from source to vm.
8. Before step 7 stop application.
9. Remove db mirroring.
10. Point application to new instance.

Please let me know if above steps are correct or missing anything.

My question is:
Do we need to keep same instance name on new vm server i.e computername\instancename or what part can we change. Computer name or instance name?
Secondly how to minimize impact on application side. I don't want that application team should change connection string at lot of places.

Thanks
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-07-16 : 18:10:22
Yes that looks good except I'd remove step 9. I would drop mirroring until a few days after you've migrated to the VM, in case you need to quickly fail back for some reason. Just make sure you use async mirroring so that you don't have the two-phase commit overhead.

Whether or not you can change the instance name is dependent upon your application. If you don't want to make app changes, then I'd use the same instance name, same port, same IP address and even same computer name. So the VM name would become the virtual name that was used on the cluster. I'd do it this way by using a temporary name for the VM. The problem with this though is that you can only change the computer name after mirroring has been dropped.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2012-07-17 : 10:22:55
Thanks Tara for your help.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-07-17 : 12:15:25
You're welcome, glad to help.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -