Troubleshooting

Full Convert Full Convert

Troubleshooting

Our converter is carefully engineered to be as fast as possible. Sometimes you may want to let it run slower in order to lighten load on your databases or avoid problems with low-quality drivers (we saw this happen with some ODBC drivers).

If you have no problems when converting, you don't need to touch anything here.

Insert 1 record at a time forces our application to send each data record to target database separately. This will be slow, but is useful when you need to find out which record causes problems. It's recommended to use SQL Error log (see Log files) when this option is checked.

Don't count table records will speed up conversion somewhat, but you lose nice progress bars when table is being copied.