F
Frank Rizzo
I am building a vs2005/c# stand-alone desktop application that will need
to store quite a bit of relational data locally. The database will be
mostly a read-only data store. This application will be distributed to
many locations, so I am definitely not going to use a server-based
product (like SQL Server or SQL Server Express), because I don't need
the installation and support headache.
So I am considering what to use. So far my choices are:
SQL Server Everywhere (cons: no sprocs or views support)
Microsoft Access (cons: has to have OLEDB Jet driver installed)
XML files (cons: have to use XPath for querying and it will probably
get slower as the amount of data increases - I can't slap an index on
the XML file).
I was wondering what folks here thought about these choices and whether
anyone has another alternative to offer.
Regards
to store quite a bit of relational data locally. The database will be
mostly a read-only data store. This application will be distributed to
many locations, so I am definitely not going to use a server-based
product (like SQL Server or SQL Server Express), because I don't need
the installation and support headache.
So I am considering what to use. So far my choices are:
SQL Server Everywhere (cons: no sprocs or views support)
Microsoft Access (cons: has to have OLEDB Jet driver installed)
XML files (cons: have to use XPath for querying and it will probably
get slower as the amount of data increases - I can't slap an index on
the XML file).
I was wondering what folks here thought about these choices and whether
anyone has another alternative to offer.
Regards