Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Please forgive me if this has been asked a million times, but I was unable to find what I was looking for with the searches I tried.
In my last job, our data specialist used DSS to migrate data from a legacy database (in Paradox, I believe) to MySql. There were a huge number of differences between the two schemas, but he was able to accomplish everything that was needed with this marvelous tool!
I now have a similar task—migrating between an old and new MySql db—but I'm having a hard time figuring out the next step(s).
I have connections to both databases, and I've added the tables from the source database to my project. At this point, I have no idea how to add the second connection (to the destination db).
Edited to add: I've been able to add datasets from both the source and destination databases but I need some guidance on what kind of recipes will allow me to modify and export data from one schema to the other. I've included a screen shot showing part of two schemas.
Any help you can offer would be greatly appreciated!
I've been working on the project this weekend, adding some information in its wiki and extending the Flow. I hope to send something by the end of the day, and hopefully we can work together or include more people in the project.
The idea remains the same: is an example of ETL to go from one schema and DB to another. It might not solve your particular case directly, but the idea is to show the available methods in DSS
By the way, what I'm trying to do here is to move from the sakila original schema:
to a new Star schema that will look like this:
By using this publicly available example dataset (sakila) we can work together on data that is safe, public and common.
Let me know if you think this is a good idea for you. Or if you were looking to work directly with your own data.