This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
on 09-27-201609:12 AM - edited on 03-08-201901:10 PM by SydneyF
How To: Migrate Entire Databases Using Alteryx
Can I? Should I?
While the answer to this question is yes, Alteryx can do that, it should only be done with a few caveats.
These caveats stem from Alteryx's need to create temp files of your data to allow for manipulation without changing your source database/file. This allows Alteryx to separate the "working" data from your "real" data (housed in the database). Basically, if you're attempting to move the data from one database to another, your entire database will be duplicated in a temp file.
1. The first caveat is time sensitivity; using Alteryx to move a massive store of data will require the processing time to write the database to temporary memory.
2. If the Alteryx workflow were to timeout, error, or otherwise be interrupted, the process would stop and the user would need to figure out where it stopped on their data. Then change the workflow to eliminate the incomplete data and start the process anew. This is the second caveat to keep in mind.
While Alteryx can do many amazing things with your data, using it to migrate entire database worth of data is a tricky operation that has to be prepared for (allocate proper temporary memory) and monitored closely. Do so with caution!