SQLite vs Excel for STD as database

I generated 360k orders yesterday and I tested it today using XLS as the database... It did not go well. So I put together a quick test "rig" to see how it would compare against the simple SQLite database. You do not need to guess what the outcome was.
Now... in the long run would I still use Excel as the medium that new data will be imported in bulk via some kind of scheduled task or I use csv file for that? I guess that would depend on how many tables/sheet you have to manage.

[@fl7422]

wow, and WHAT a difference it is!

[@gebsystems]

Totally! Seems like running SQL queries via ODBC is not very efficient if you wanna go through a significant amount of rows. SQLite seems like a work horse in comparison.

[@BB-sm8ey]

A database is designed for speed, but that doesn't invalidate your idea. Generating a system from a spreadsheet is something within the grasp of almost any business or organisation. You just need a way, once the clients are comfortable, to fix up the "prototyped design" in a DB. There won't be more than a few 10k rows before that point in most cases.

[@gebsystems]

I am just toying around so far. I build few tools that make the experience more bearable and they are included as download links in the youtube videos. Now I am putting together a "proper" demo which evolved from my first DIY intranet idea to provide a general feel of how this could work. Next will show how to migrate it to a SQLite backend and use Excel / CSV as the import tool. I am obviously trying not to loose to many people on the way with this :) Maybe someone will find it useful at the office they work even if it means that it helps just them with the workload.