When / why should I start using the database?

I am currently evaluating the design and the possibility of re-equipping my own application, which our engineers use.

Although the application processes large amounts of data. Only two sets of values ​​(floats) are stored along with a simple name and data description. In my opinion, the current application is located in the overflow area using a normalized access database for storage, which evaluates 7 rows and floating fields.

At what point do you start looking at the transition from a flat file or serialized XML to a relational database, or vice versa?

+5
source share
5 answers

, ​​ SQLite, .

http://sqlite.org

+7

, .

, - , , .

+4

db - : s ( )

ACID , , clobber . , , RDBMS " ".

+3

. 7 - . 7 , ( 7 ), , .

+3

, .

When you start with many-to-many or many-to-one relationships in your data, it's time to think about using a relational database to maintain relational integrity.

+2
source

All Articles