Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
up vote -3 down vote favorite

Main problem I can think of is not migrating all the data accurately (e.g. not migrating data to the right place in the new database, or losing data in the migration process).

Other possible problems I can think of: eliminating redundant data (e.g. identifying and resolving duplicates); that there is no use of the database while the migration takes place, and data glitches.

I would be very grateful if anyone could add to this

share|improve this question
Not very clear what exactly is the question and the problem to be solved. There is no generic solution to a data migration project except: test, test, test! – Marian Feb 5 at 21:17

closed as not a real question by RolandoMySQLDBA, Phil, dezso, Jon Seigel, Marian Feb 5 at 21:16

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.

1 Answer

up vote 0 down vote

It depends on source and target RDBMS. There are some tools but they wont give you an 100% accuracy. Tables, indexes, constraints, even triggers may be migrated on an automated way. But procedures and functions can not. I'd be helpful if you added more information about which rdbms are you migrating from and to. so we could give you more accurate information about the process, but trust me, it is not reliable to trust on automatic conversions.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.