June 3, 2013 at 5:58 am
That's quite a job to be assigned. I don't know of any automated tool that would do the whole job. I would probably opt to do it table-by-table, view-by-view, etc. creating the tables, indexes, etc. writing the SQL for each one. I know this is a lot of work and would take considerable time for a complicated source database.
As you write and update it, this script would be the migration script for when it comes time to release. The approach lends itself very well to testing multiple times and you can compare your test database to your original source as many times as you need to.
As for an automated tool, if anyone does find one that does the job, please share what you learn. I'd be very interested in it.
June 3, 2013 at 8:15 am
I may suggest views and leave the base data alone. This would cut down on project time and would only need to update the references in the Sprocs, functions, etc.
SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply