Comments on: a monumental migration to sql server 2016

By: Andy Levy

Andy Levy — Thu, 23 Apr 2020 01:22:37 +0000

Thanks! I don’t have the code for that function anymore, but you can see something close to it in the post on my blog where I demonstrated PoshRSJob. That is available at https://flxsql.com/powershell-multithreading-with-poshrsjob/ – scroll down to “Bonus Round”.

By: bhaktapur

bhaktapur — Wed, 22 Apr 2020 20:30:28 +0000

Andy, great job. I am thinking of applying your method to move around 1500 databases to new server. In your description above you mentioned about Get-MountProgress. Do you have the script for that?

By: Marcin Gminski

Marcin Gminski — Wed, 13 Mar 2019 21:57:03 +0000

Over EIGHT THOUSAND databases on one server? Wow. I can imagine the startup time…well, I can imagine a lot of things on that box… anyway, Great read and good job with the migration!

By: Andy Levy

Andy Levy — Fri, 18 Jan 2019 02:48:16 +0000

Yes, the new server was set up as a completely new box. New hostname, new IP, everything. The old server was not taken offline/powered off/removed from the rack for about 3 weeks after the migration was completed. The issue with the app is that it had a connection string embedded in the code which we were not aware of.

In some respects it would have been easier if we could have kept the same hostname and IP, but that was not an option for this project.

By: Andrew Coffman

Andrew Coffman — Thu, 17 Jan 2019 16:18:34 +0000

Andy, great post and scripts. I’m new to powershell, but was curious about your approach to the common and complex migration challenge. In your scenario, you mentioned some apps were still pointing to the old server. Did you have to create a new DNS for the destination server instead of changing the IP for alias?