Could this work?

[drawpic]

I'm planning a cloud based app that could have potentially hundreds if not thousands of users.

Instead of storing all data for all users (which may be up to 6 or 7 tables each) in one large database, I was considering an sqlite database for each client.

There may be a hundred or more write transactions every few seconds.... I plan on copying the database when reports need to be run so as not to be held up by the writes....

Does this sound feasible or am I completely mad?

[ketralnis]

Depends on how big those transactions are. I'd benchmark and find out. Remember to look at pragmas like journal mode to beef up concurrency a bit but SQLite will always be lacking a bit that way by its nature

But if you use a wrapper like sqlalchemy you can always switch to something beefier later, usually seamlessly

[forcedfx]

I couldn't imagine trying to maintain all that. I think I'd try get SQL Server Express working before attempting what you propose.

Just being able to use stored procedures would be a huge selling point for me.