dom_bus
asked on
Architecture Design Question : use a Database or not?
Hi experts,
I'm about to redesign an application that exists, but doesn't run properly and I wonder whether I should use
- a database to control/store my data,
- only store my data or
- no database att all, but only the object structure in the program language combined with serialized dumps.
the data i'm talking about would correspond to ca.
- 10 smaller tables (5 fields X max 50 rows)
- three medium size tables ( 30 fields X max. 200 rows)
- one bigger table (50 X max. 5000 rows)
the application should be able to run "standalone" (withour network-access) on the other hand we made some bad experience with mdb files!! (field.nullable returns wrong values depending on what OS you run the app. on)
thanx for you opinions.
dominik
I'm about to redesign an application that exists, but doesn't run properly and I wonder whether I should use
- a database to control/store my data,
- only store my data or
- no database att all, but only the object structure in the program language combined with serialized dumps.
the data i'm talking about would correspond to ca.
- 10 smaller tables (5 fields X max 50 rows)
- three medium size tables ( 30 fields X max. 200 rows)
- one bigger table (50 X max. 5000 rows)
the application should be able to run "standalone" (withour network-access) on the other hand we made some bad experience with mdb files!! (field.nullable returns wrong values depending on what OS you run the app. on)
thanx for you opinions.
dominik
ASKER
cryptosid : o.k. but why "will it be good" for me ?? instead of database tables i could use hashtables, arrays or vectors, couldn't I?!?
Every method has its pros and cons u should consider all the factors in mind eg
currently u require around 5000 rows what if tommr it increases to 10,000 or more...if u have the slightest probability that they might increase its better that u go for databases.
Databases will provide u simple solution for ADD/MOD/DEL of info with their inbuilt consistent methods u don't need to worry about anything...
If u are really good at programming u may use hash tables and other stuff but mind u the more the number of records more is the time complexity and simple stuff...its a matter of ur choice...
best of luck
cheers
currently u require around 5000 rows what if tommr it increases to 10,000 or more...if u have the slightest probability that they might increase its better that u go for databases.
Databases will provide u simple solution for ADD/MOD/DEL of info with their inbuilt consistent methods u don't need to worry about anything...
If u are really good at programming u may use hash tables and other stuff but mind u the more the number of records more is the time complexity and simple stuff...its a matter of ur choice...
best of luck
cheers
ASKER
at the moment the people who will work with the app. do everything more or less manualy and they have only a few dozen of entries in the "biggest table".
=> max. 5000 / max. 200 really IS the max we ever expect within the application life time.
add/mod/del seems to be pretty simple in hashtables as well, so what more are reasons to use a database or not use a database?
dominik
=> max. 5000 / max. 200 really IS the max we ever expect within the application life time.
add/mod/del seems to be pretty simple in hashtables as well, so what more are reasons to use a database or not use a database?
dominik
Well in that case the only advantage databases provide is consistency of updates! but since the database is not going to be on a network u may use hash table instead ( if u are comfortable with it go ahead)
cheers
cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if u don't wanna use a MDB files u could use other options...
create it in C/C++ use file operations to ADD/DEL/MODIFY
or
use dbase 3+ (if u can get one version of it) but it is very good and provides enough set of commands.
or u could use any other database other than MDB...