Re: when to use a DB

In message <5d146344.0203061320.477b78f4_at_posting.google.com>, siva chelliah <podian_at_yahoo.com> writes
>When you start a project, sometime you discuss if we need a DB or not
>for that project.
>
>What are the guidelines on when to use and when not to use a database
>for your projcet?
>
>I do not want to use a DB and incur un-necessary overhead. So I want
>to make sure I really need a DB in our current project we are just
>starting to design.

One of the things you should consider is whether the developers you have available understand databases. If you have someone who is a genius at programming spreadsheets then you may find it easier to develop applications using a spreadsheet to store your data.

Personally, I use a database whenever I have to store column-based data and there are more than around 20 rows. That's because I can build simple databases really quickly.

Why do you think that you might need a database for this project?

-- 
Bernard Peek
bap_at_shrdlu.com

In search of cognoscenti