Thursday, 10 November 2011



A database is a collection of information that is organized so that it can easily be accessed, managed, and updated. In one view, databases can be classified according to types of content: bibliographic, full-text, numeric, and images.
In computing, databases are sometimes classified according to their organizational approach. The most prevalent approach is the relational database, a tabular database in which data is defined so that it can be reorganized and accessed in a number of different ways. A distributed database is one that can be dispersed or replicated among different points in a network. An object-oriented programming database is one that is congruent with the data defined in object classes and subclasses.


The type of database system or tool that you require depends on a number of 
factors, such as: 
- the complexity of the data involved, eg plain text, images, sound files 
- the quantity of data to be stored and processed 
- whether the data needs to be accessed and amended by more than one 
person simultaneously 
- whether data needs to be imported from, or exported to, other IT systems.

If your requirements are simple, eg monitoring the names and addresses of 
around 100 customers, you might find that standard office tools such as a 
spreadsheet might be all you need. 

Why database?

One thing I've been curios about is why do you use sql thingys and the like when you could just use an array?
: Are they just for making programming easier so you don't have to worry about memmory, or is another point?
: There's a lot of problems with database and a lot of people who got problems with it, so maybe if everyone would trash it away the problems will be gone...

 Sure, a database can help a lot. But from my opinion today most people use a database in their applications because it's somehow *chic*. There is no real use for a database, but you have to - maybe 'cause an application without a database isn't a real application.
You can avoid alot of problems with using plaintextfiles/arrays and things like this. A database should normally only be used if there is a need to do so (high performance, a lot of data stored).
A database can help but you should think about it because it brings also much trouble and complexity with it.

Database career path

  • Administrator    
  • Database Administrator (DBA)   
  • Oracle Database Administrator   
  • Oracle DBA   
  • SQL Server Database Administrator   
  • SQL Server DBA 
  • Data Analyst
  • Data Designed
  • Data Technician
    Why are Databases Important?
     • Data -> Information -> Knowledge
     • Efficient Manipulation of Large Data
    • Integration of Multiple Data Sources
    • Cross-Links/References to Other

No comments:

Post a Comment