Access databases are not loaded completely in memory, it sounds like
your XML is. Depending on the size of your database, this could go
either way. small database would favor your xml probably, large would
definitely favor the Access db.
Larger databases lend themselves to RDBMs, such as Jet, which Access
uses as its database engine. Larger databases also lend themselves to
SQL databases.
generally, the larger the dataset, the more you would want to go with an
sql database. the smaller the dataset, the more reliably you could use
a flat-file database, such as XML. Jet (a.k.a. Access) DBs are
generally regarded as a small to mid-tier databases.
hope that helps.
Benny Raymond wrote:
I'm nearly done writing the first version of my tracking app and I'm
starting to re-think the way I store my database. Currently I have my
database setup as an xml dataset. Before I started the program I choose
to go with a dataset because I was unclear if the end user would have to
have access installed if I went with an access database.
Recently I'm starting to realize (or think) that this isn't the case.
And, from what I gather, the xml dataset is loaded completely into
memory while an access database would not be loaded completely into
memory (please correct me if I'm wrong).
I'm also not sure which is faster.
If those of you who have experience with both, or either, could
enlighten me I'd really appreciate it. From what I've seen in access c#
code samples, it wouldn't be that difficult to convert my app to use a
different type of database.
If you have different suggestions that aren't just xml or access please
also let me know.
thanks
Benny
