This among other things gets rid of username/password issues and other admin problems. A short script to import a fixed-width file doesn't sound like any big deal. Most SQLite utilities import .csv files. One approach would be a simple filter to make your fixed width input file into a .csv file. And then use an import tool on that file. Another approach is shown here: import-fixed-width-text-file-into-sqlite.
As long as the SQL features being used in the MySQL program are available in SQLite, SQLite should provide a smaller footprint solution and work very well.
Update:
You say that this file is an industry standard fixed width format. Ok show say 3 lines of data, some spec on what the columns should be named - maybe schema from your MySQL DB? We could help you with the code to import that data if you are having trouble doing that. If speed matters, the main thing for import is to minimize the number of transactions. I usually run 150K-250K rows per transaction although even a million is fine. There may be some datatype issues in the port (like datetime type) but there are solutions to all of those things. You will be impressed with SQLite performance.
In reply to Re: Perl DBI for MariaDB v SQLite in a Single Use SBC
by Marshall
in thread Perl DBI for MariaDB v SQLite in a Single Use SBC
by justin423
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |