The new Data Migration Assistant has been released!

, 2016-08-31

Monday Bob Ward (b/t) announced on twitter that the new Data Migration Assistant had been released.


First things first the DMA is a replacement of the Upgrade Adviser. In fact it’s an upgrade of the Upgrade Adviser. It has some amazing new features.

  • You can install this on a workstation. It doesn’t have to be installed on the server itself.
  • You can have multiple projects saved with data from multiple server/instances.
  • There is the option to get compatibility issues and/or new feature recommendations.
  • You can check issues/feature recommendations for upgrades to 2012, 2014 or 2016.


The next really cool thing about it is that it’s v 1.0!!!!! This means that we can expect improvements from here! In fact there is a Migration option grayed out with Coming Soon right next to it. So it looks like in the future not only will this tool give us a list of possible issues with the upgrade but will help with the upgrade itself. I’m also hoping (although I haven’t read anything that says yay or nay) that Azure migrations will be included in the tool as well.

Oh, and I should point out that I’ve been working on a migration from 2008 R2 to SQL 2016. I installed the Upgrade Adviser on the server (including a new version of .Net) and tried to run it. Unfortunately I quickly received a error due to some bad characters in the code.


At this point I was stuck. I didn’t have the name of the objects to even try to look at what the errors could be. And with 600+ objects it would be difficult to find them.

Well guess what? I ran the DMA and while the errors showed up they did not stop me from running my report. Not only that the errors had the specific objects listed as well which meant I could find and correct the bad characters.

One brief warning. I did get a login failure (with no detail) when I attempted to connect as something other than sysadmin. Hindsight it seems pretty obvious why it requires sysadmin but it still took me a few minutes to figure out.





Filed under: Microsoft SQL Server, SQLServerPedia Syndication, Upgrades Tagged: microsoft sql server, upgrades





Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.


1,567 reads

Networking - Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I'd like to talk about social networking. We'll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let...


1,530 reads

Speaking at Community Events - More Thoughts

Last week I posted Speaking at Community Events - Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I've got a few more thoughts on the topic this week, and I look forward to your comments.


360 reads