Text file vs DB

25 Oct 2006 7:14 PM

Daniel

Hi all,

I am designing an app to run on Windows Mobile 5 using VB.NET 2005. The
app will make use of a couple of static tables for reading data and 1 table
of data which the user will modify. Currently I am trying to decide how
best to store the data.

I saw that Microsoft has released a CTP of SQL Everywhere which they say
is perfect for mobile devices. It looks really good and I immediately decided
to use it. Then, I had a bit of think about it and now I am not so sure.
My DB will have around 4-5 tables with no more than 1000 records in 1 of
the tables and the other tables being much smaller. My app runs, loads the
big table into an array (Would I benefit from using SQL and not loading the
array into memory?) and then works on it. So, does anyone know if I would
benefit from using the SQL database or if I'd be better off sticking with
simple text files/XML files to store my data? I want to choose the fastest
solution, not the most elegant nor the one that requires the least code.
My biggest concern is speed of data access and also size of DB's.

The app does simple text searching and storage of text values from a reference
DB, nothing complicated with the database.

TIA

Daniel
---------------------------------------------------
To contact me you need to clean up my email address. It should be fairly
obvious...

25 Oct 2006 10:11 PM

Dick Grier

Hi,

>>

My app runs, loads the
big table into an array (Would I benefit from using SQL and not loading the
array into memory?)
<<

I think this is one of those, "It depends, answers." However, my best guess
is that it would be easiest to simply leave it in the ResultSet that you
created when you load the table. I'd use an array or collection (or other
list) only if the data was used to populate an object that has more complex
behavior.

>>

So, does anyone know if I would
benefit from using the SQL database or if I'd be better off sticking with
simple text files/XML files to store my data? I want to choose the fastest
solution,
<<

SQL will be easiest to use and expand. Fastest? Maybe, maybe not...
Reading a XML file may be fastest. Updating the XML (which will require
re-writing the entire file) may be slower. I don't think there is a simple
answer.

Dick

--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See www.hardandsoftware.net for details and contact information.

26 Oct 2006 4:38 PM

Daniel

Show quote Hide quote

> Hi,
>
> My app runs, loads the
> big table into an array (Would I benefit from using SQL and not
> loading the
> array into memory?)
> <<
> I think this is one of those, "It depends, answers." However, my best
> guess is that it would be easiest to simply leave it in the ResultSet
> that you created when you load the table. I'd use an array or
> collection (or other list) only if the data was used to populate an
> object that has more complex behavior.
>
> So, does anyone know if I would
> benefit from using the SQL database or if I'd be better off sticking
> with
> simple text files/XML files to store my data? I want to choose the
> fastest
> solution,
> <<
> SQL will be easiest to use and expand. Fastest? Maybe, maybe not...
> Reading a XML file may be fastest. Updating the XML (which will
> require re-writing the entire file) may be slower. I don't think
> there is a simple answer.
>
> Dick
>

Thanks Dick.

Daniel
---------------------------------------------------
To contact me you need to clean up my email address. It should be fairly
obvious...