Saving Time with SQL Server Migration Assistant for Oracle

After using the SQL Server Migration Assistant for Oracle on a current project to migrate an Oracle database to SQL Server, I have learned a couple of little tricks that I would like to pass on to you.  These are mainly time savers so hopefully they will make you more productive in your project.

The first problem I noticed is that there was no easy way to copy projects nor was there a way to save a project file as another name, which would have allowed me to copy the project.  Why would I want to copy a project?  There are many settings such as column type mappings that will stay the same for my project and are very time-consuming to enter, if you are modifying the defaults.  In my migration, I want to do many iterations in my development and acceptance environments with different SQL Server database names such as Round1, Round2, or Round3 and then use Red Gate Compare and Data Compare to verify that all of the schema and data from the migration are consistent in my migration.  This gives me a warm and fuzzy feeling before I turn over the data to the testers. 

However with each iteration, I must create a new project manually.  Why?  Because SSMA does not refresh to recognize new databases in the existing projects.  That is very annoying.  It only shows what is there  at the time the project is created.  Even if you reconnect to the SQL Server, it does not refresh. 

If you know ahead of time that you will do many iterations, you could however create several databases before starting with the SSMA and then copy the project folder from the first project that you create manually.  You must then rename the folder to the new project name and the corresponding project file (with an o2ssproj file extension) contained within the project folder.  This would allow you to simply switch to the new database.  You must also keep in mind that you need to double-click on the Oracle schema and make sure the target schema is selected as your new database.  This will not happen automagically as you choose a new database name in the SQL Server metadata explorer.

Another option is to create new projects as you create the databases and then copy in the object-container.mappings and/or project-container.mappings files from the first project folder into the new project folder.  This will allow you copy those settings into the new project and save you some time.  I hope you find this useful.  Enjoy.


About SQLGator

Microsoft Data Platform MVP, Florida Gator, Star Wars fanatic and is there anything else...oh yeah PS4! I am a geek and SQL Server Business Intelligence Consultant, there are other technologies greater than these? Not so fast my friend! I also love to travel to new and exotic places.

Posted on August 2, 2012, in Migration and tagged , . Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: