Current version of our application holds data in MySQL. We have a new version, which is developed in Flowable.
What is the best way to migrate data from MySQL to Flowable?
Is there any APIs available to do this task?
If not, is there any
documentation about how to design an ETL process to load data to
Flowable?
I can see Flowable Database schema in their documentations but I couldn't find any clue about migrating data from an external system to Flowable. Any help will be much appreciated.
Flowable is not a database therefore migrating data from MySQL to Flowable is not something that can be done.
Flowable supports storing its data in different Databases.
What you are most likely looking for is migrating your business logic to Flowable. There are ways to do this using the Flowable Java APIs in order to bring your old business data in the new state you will need using Flowable.
There is no specific documentation for this because this highly depends on your own business needs.
Related
Hi This question might be too broad for stack overflow community. If anyone can give me suggestions about it that would be very helpful.
I am currently using mongodb as my active backend for all the operations part. I am planning to use postgresql or mysql (whichever feasible in my case) for the reporting and analytics purpose as well as syncing it locally with my Desktop application to display data on client side.
I tried MOSQL but it seems like MOSQL doesn't support mongodb v3.0.
I figured out how to pass data between mongodb and postgres via a python script. But could figure out how to pass selective data when new data comes.
Can anybody help me with some tool or script which can help me setup a replication of mongodb in Postgres or Mysql?
We have a rails app that has a MySQL backend, each client has one DB and the schema is identical. We use a custom gem to change the DB based on the URL of the request (This is some legacy code that we are trying to move away from)
We need to capture some changes from those MySQL databases (Changes in inventory, some order information, etc) transform and store in a single MongoDB database (multitenant data store), this data will be used for analytics at first, but our idea is to move everything there.
There was something in place to do this, using AR callbacks and Rabbit, but to be honest it wasn't working correctly and it looked like it was more trouble to fix it than to start over with a fresh approach.
We did some research and found some tools to do ETL but they are overkill for our needs.
Does anyone have some experience with a similar problem?
Recommendations on how to architect and implement this simple ETL
Pentaho provides change-data-capture option which can solve Data-synchronization problems.
If by Overkill you mean Setup, Configuration, then Yes that is the common problem with ETL tools and PENTAHO is the easiest among them.
If you can provide more details, I'll be glad to provide an elaborate answer.
I want to retrieve data from remote MySQL database and store the data in my iOS app (creating "local" database, so the information can still be accessed even though there is no connection). After doing some research, Apple's Core Data API seems to be the answer. However, it's using SQLite.
Can I use Core data with MySQL? If the answer is no, is there any way to develop "local" database other than Core Data? I tried looking for the answer, but no luck. This is the closest one that I can get, but I don't really understand the answer. I am new at iOS development, so any help is greatly appreciated.
Yes, you can use Core Data with MySQL if you like, but you need to write the persistent store functionality yourself, which is a fairly advanced undertaking. It doesn't seem to have any benefits though. I think it would be better to retrieve the data from the MySQL server, and then store it locally in Sqlite. MySQL requires a separate server so obviously it cannot be run locally on iOS anyway.
You cant use coredata with MySQL. Because CoreData is a local database inside the mobile and MySQL is WebServer database. So we cant combine them. Why you dont like CoreData? It is the most powerful and simple database for the mobile apps. I think CoreData suits for your purpose. If your data is something lightweight. Then you can use
Plist
http://hayageek.com/plist-tutorial/
http://www.theappcodeblog.com/2011/05/30/property-list-tutorial-using-plist-to-store-user-data/
NSCoder
http://www.raywenderlich.com/1914/nscoding-tutorial-for-ios-how-to-save-your-app-data
CoreData is the way to go. CoreData is build under SQLLite but it is a relational data base --> Object Oriented mapping which makes it really convenient.
There's a graphic editor which will allow you to define your CoreData model the way you require it.
this is the situation:
I have two server: development server(intranet) and production server(internet).
Authors are inserting data in the production server, on daily basis.
Developers are upgrading the DB structure according to the new web app releases projects.
The problem is: when a new web app is released, I must synchronize the data online with the offline db (updating data). Before upgrading online scripts and db structure.
Is there a better way to perform this merge than a sort of manual/editing/updating via some sql scripts?
Doing it manually is also risk-prone since: sometimes I may lose track of exactly what tables contain newer data and have been updated since the last upgrade...
Note: MySQL replication won't be the solution, since it means it will update data but destroy new structure on development DB.
Many thanks in advance
Try to view differences and synchronize data between two databases with Data Comparison tool in dbForge Studio for MySQL.
How do I convert a Microsoft SQL Server database backup file such that to import in MySQL database? Is there any way or free tool available for this?
Not sure about how complex a database you have, but if its just some tables and data, there is a free script here that will automagically convert Microsoft SQL Server tables and data over to MySQL.
If you need something more sophisticated, then MySQL has a migration toolkit which allows you to migrate from Microsoft SQL Server to MySQL. In addition here is a tutorial on how to use it. Note that this has now been discontinued, in favor of MySQL Workbench, which has data migration built in.
In addition, this converter will convert everything except stored procedures from MSSQL to MySQL, for a price of only $50 which isn't bad.
Also you may want to check out this whitepaper from MySql's website on how to plan a migration from SQL Server to MySQL, as well as some resources.
ms2my (Pre-Alpha, free)
http://sourceforge.net/projects/ms2my/
"A tool that helps with MSSQL to MySQL converting/replicating (both csv&dump) under *nix.Possible to use it with crontab for regular data fetching.Keeping mySQL-based data warehouse refreshed could also be one of the possibilities of using this script."
MSSQL to MySQL Converter (free trial download, for purchase $49)
http://www.convert-in.com/mss2sql.htm
I've looked for quite awhile, and if you don't want to try ms2my, the above is about the only other option. And it isn't free.
Best of luck finding a free one, hopefully there is one that is hidden away out there on the internet that I can't find.
If you are using a living MS SQL Server and a living MySQL server, then I think your best AND MORE ACCURACY option is to use an ETL/data transformation tool like Pentaho Data Integration (Kettle).
With Kettle you can visually design (using easy-to-learn data flow steps) almost any data transformation from single/multiple data source(s) to single/multiple data destination(s). One of the features you may be interested is the database/tables migration wizard.
If the community distribution of Kettle is not enough for you, then you can use the Enterprise Edition with more features, support, etc.
Take a look at Omega Sync it supports export import and synchronisation between different DBMS's including Schema and table data.