Quote:
Access doesn't fit because he doesn't treat multiple read-write very well.
SQLite and compact SQL won't fit as well.
|
Well, Acess is a software built around the JET engine, and not designed to be used in an highly parallalized environment.
SQLite can, but as it's working on a binary file, it does read lock on every insert or update that is sent, whcih can impair throughput on really really busy sites.
If I where you, I'd avoid sql express 2005.
It's not a bad product, not at all, but if you go the sql server road, go with sql server 2008. It exists in express edition too.
Personally, I'd choose postgresql.
http://www.postgresql.org/
It's a relational DB engine that have more than 12 years of development behind it.
It's fast, flexible and stable with a native Windows version.
Support a whole lot of extended features, can be easily setup in a replication mode and distributed nodes.
http://www.postgresql.org/about/featurematrix
The same to sql server, yes, but where the sql server express edition is limited (memory, number of cpu used), postgresql is not.
I work as an sql server DBA, and one of my co-worker is that kind of person you refer to with "the guru".
That guys seems to know everathing about sql server, and it's really impressive to work with him.
I presented him postgresql once, when I just arrived in the team, and he's comment after 2 hours of play with it was
Quote:
|
it's a pretty impressive software.
|
Already way more than I was expecting...