Feedback from customer related with DBMoto:

Everything was good. Would like to state again that some value would be generated by writing out the records that error out into a format that can be used to apply to the target database. For example, a table had a time out error this morning and the record it was trying to update was put into the log file with all of the fields and their values. If that could be made into an INSERT/UPDATE formatted statement (string quoted...) it would make validation much easier. I also did just notice that DBMoto itself doesn't seem to have written a failed record in that instance into the history file for the display in Management Center. I will send an image showing this separate. Another option would be to create a table in the DBMoto_Client database that would be an empty shell of the mirrored table. Then write errors into that table (similar to Access on an import) which would then allow the user to use standard SQL for the needed operation. Put a hold records for setting to keep the tables from getting too large. This could also speed up recovery because error writes for a table throwing thousands of errors can cause a backlog on the mirroring cycles as they wait for that to recover. I did this with a table defined wrong on the target side so as it tried the replication every record was throwing an error and when it was disabled all of the running mirror sessions were held until the bad records were written to the log files.