This topic has been locked.
4 replies Latest Post - 2012-12-05T20:16:19Z by loicjulien
Pinned topic using Migrate -> Compare & Migrate Objects with large catalogs
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
When I use Migrate -> Compare & Migrate Objects with two databases that have very lareg catalogs (5000 - 6000 tables each), this wizard never comes back within a reasonable amount of time. I've let it run overnight, and it's still not returned anything. Any tips on how to speed up the migration? I choose a schema for a source object to compare.
Updated on 2012-12-05T20:16:19Z at 2012-12-05T20:16:19Z by loicjulien
atimpo 2000004VK116 Posts
loicjulien 2700007DEB96 PostsACCEPTED ANSWER
Re: using Migrate -> Compare & Migrate Objects with large catalogs2012-12-05T20:14:25Z in response to atimpoHi,
Since Data Studio will need to load most of both catalogs in memory before it can start the comparison, I wonder if you need to do a full comparison or if you could set a Catalog filter in order to work with a smaller set.
We had written an article on how to enable such a filter last year. Adding it here, as a reference, as this may further help you: http://www.ibm.com/developerworks/data/library/techarticle/dm-1109datastudiodbcatalog/index.html
This is slightly different than setting filters in the Compare/Migrate dialog, since the comparison may still involve objects that could lay outside of the objects selected within the wizard (cross schema RI, ...)
Setting a Database Catalog Filter allows Data Studio to never load portion of the catalog to start with.
Let me know if you would like to further talk about this, so that we can help you with your use-case.
You can reach me at [http:// lj -- AT -- us.ibm.com ]