Frequently Asked Questions
Is this an Excel–PostgreSQL integration or a one-way load?
A one-way load, on purpose. The Excel–PostgreSQL integration people usually mean is a live link (ODBC driver or a foreign data wrapper querying the workbook from inside PostgreSQL), which keeps the file as a moving part and needs a driver on every machine that refreshes it. Importing the rows makes the table the permanent copy; re-run the same saved session when the workbook changes.
Can I connect Excel to PostgreSQL and refresh from inside Excel instead?
That is the other direction: a live Excel–PostgreSQL link needs an ODBC driver and a query kept inside the workbook, which holds a server connection open. Here you export the Excel rows into PostgreSQL once, or on a schedule — the table becomes the source of truth and Excel stops being the loader.
Do I need to install Excel?
No, FileToDB reads Excel files natively without Microsoft Excel.
How do I schedule a folder of workbooks to load every month?
Save the run as a session, then call it from the command line and let cron, launchd or Task Scheduler start it on the first of the month. Keep the folder layout and the header row stable — the session matches column names as they were when it was saved.
Is my data safe?
All processing runs locally. No data is uploaded to any server.
Can I run on Linux/macOS?
Yes, full support for Windows, Linux, and macOS.
What PostgreSQL versions does FileToDB support?
FileToDB support PostgreSQL 9.x, 10, 11, 12, 13, 14, 15, 16, 17, 18.
Can I automate daily imports?
Yes, save sessions and schedule via system task tools.