Kexi/Handbook/Introduction to Databases/Who Needs a Database?: Difference between revisions

From KDE UserBase Wiki
(Marked this version for translation)
(don't use sections)
 
Line 3: Line 3:
===Who Needs a Database?=== <!--T:1-->
===Who Needs a Database?=== <!--T:1-->


====Stick to spreadsheets if:==== <!--T:2-->
'''Stick to spreadsheets if:''' <!--T:2-->


<!--T:3-->
<!--T:3-->
Line 14: Line 14:
* You use complicated spreadsheets and you lack time or money to switch to databases. Think or ask someone whether this does not lead down a blind alley. Don't count on magical tools that would change your spreadsheet (regardless how well made) into a database.  
* You use complicated spreadsheets and you lack time or money to switch to databases. Think or ask someone whether this does not lead down a blind alley. Don't count on magical tools that would change your spreadsheet (regardless how well made) into a database.  


====Consider using databases if:==== <!--T:6-->
 
'''Consider using databases if:''' <!--T:6-->


<!--T:7-->
<!--T:7-->

Latest revision as of 22:17, 27 August 2014

Other languages:

Who Needs a Database?

Stick to spreadsheets if:

  • Your needs are limited and your data will never grow to large volumes (can you actually forecast that now?)
  • You are unable to acquire the methodology of database construction. You may however consider either outsourcing this task to someone else or using simpler tools.
  • You use complicated spreadsheets and you lack time or money to switch to databases. Think or ask someone whether this does not lead down a blind alley. Don't count on magical tools that would change your spreadsheet (regardless how well made) into a database.


Consider using databases if:

  • Your data collection expands every week.
  • You often create new spreadsheets, copy within these and you feel that this work is getting more and more tedious. In this case the effort of switching to databases easily pays off.
  • You create reports and statements for which the table view of a spreadsheet is not suitable. You can then consider switch to using a database with form views.