Link to home
Start Free TrialLog in
Avatar of adamchicago
adamchicago

asked on

What is better to use a text file or sql db for data intensive app?

I'm building an application that will allow the user to import and name a hand full of data files (Excel data) each with a max of approx 10000 records, then the application will:
- compare record keys across the imported data files and report out what is missing between each data file and what is extra
- do some summing, division, max, mins, averages across all records in all tables
- remove and add several records across all data files depending on what's missing or extra across all data files
- rebuild all of the imported data files into a one file output

The user will import all of this data, run the application and take the output, then will do another project the same way, and then another and another each with different data and data files...sort of like creating Excel spreadsheets for various projects...each file is a totally different project, not the re-use of the same data or data structure

My question is: What is the best type of flat DB to use in terms of speed for user, ease to build the application? : text files, sql db, other?

Thank you very much!
Avatar of chapmandew
chapmandew
Flag of United States of America image

sql database...FOR SURE.  you can use sql express...its free!
I agree with chapmandew...text file only to use for keeping very small pieces of data. For structured data, use an database engine like SQL Express. As said, it's free and ideal for small applications.

jppinto
Avatar of adamchicago
adamchicago

ASKER

If the user begins a project which generates a SQL DB, can they have complete freedom to save the SQL DB anywhere on their computer and then possibly copy and paste it to a new location and reopen as easily as a text file or as easily as an MS Office app such as Excel, PowerPt etc?
Not with SQL Server. Of course, why would you need to do this with a relational database?

You can do this with an Access database ...
No, doable but not easily.

For 6 times 10000 records Access/JET will definitely be the fastest datastore.
And this single mdb file can be copied and moved just like any text file.

/gustav
For what you want to do...Access is the best option for you. It's fully integrated with other Office tools.
I want to stay away from a paid licensed DB provider such as Access because not all users of the this app will have an Access license.  From what I understand if the app uses a SQL DB, anyone who downloads SQL Server Express for free from the MS website will be able to use this app without having to purchase any kind of DB license...am I wrong?
SOLUTION
Avatar of Gustav Brock
Gustav Brock
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
So what is the advantage of using a MDB (Access like DB) versus a MDF (SQL DB)?   Which one offers more file portability for the app user (VB.Net app I'm building) and which one has more robust analytics (VB.Net app will process data faster and is easier for me to build)?

Thanks again...I've already sunk a number of hours into this app and just want to make sure I'm on the right  path;)
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for your help!
These were not B answers....