Answers to: Feature Request - Enhancement of Migrate Database tool<p>The "Migrate Database" feature allows you to specify or create a remote server and import all of its tables into the current database.<br> </p> <p>It seems to do this by creating the necessary proxy tables and selecting the data from each into local tables with the same name.<br> </p> <p>In our migration scenarios we frequently find that we have tables of the same name in both the local and remote databases. In our scenarios we want to keep our own structure's naming standard, so the remote table would be the one to rename on import. When adding a proxy table manually, you have the option to rename it, but this option is not available using the migration wizard.<br> </p> <p>What would help a great deal is an option to add a prefix or suffix to each imported table name. For instance I could prepend each imported table with S_ so that they all are labelled as source tables for further manipulation of the data into our structure.<br> </p> <p>When I don't have duplicate table names it works great, so thanks for a great tool.<br> </p>enMon, 04 Mar 2013 10:57:36 -0500Answer by Karim Khamis<p>Your enhancement request is a very valid one and will certainly be considered for a future release. In the meantime, you could consider creating a new user or group to own all the migrated tables and then specify that user as the table owner in the migration wizard. Then it should not matter whether a table with the same name already exists because the table owner of the migrated tables will be the new user or group. I realize having a different owner for the migrated tables might be a pain, but it would get you beyond the current issue.</p>Karim KhamisMon, 04 Mar 2013 10:57:36 -0500