Difference Between Flat File & Relational Database

Written by deborah lee soltesz Google
  • Share
  • Tweet
  • Share
  • Pin
  • Email
Difference Between Flat File & Relational Database
Table structures in databases organise data in rows and columns. (number background image by kuhar from Fotolia.com)

A flat file database stores data in a single table structure. A relational database uses multiple table structures, cross-referencing records between tables. Tables in both organise records in rows, with each column containing a single piece of data in the record.

Other People Are Reading

History

Flat file databases were a natural development early in computing history. The relational database model was developed and implemented in the early 1970s, primarily by IBM.

Flat File Databases

Flat file databases are typically plain text files that store one record per line, with record fields delimited by whitespace or a delimiting character. Flat file databases can be read directly by a variety of software applications.

Relational Database

In addition to the data tables, relational databases use "indexes" to quickly find records based on search criteria. Relational databases generally require a relational database management system (RDBMS) to manage and access the data.

Benefits

Flat file databases are simple and portable, and typically can be used without requiring special software. Relational databases are faster, more efficient and more powerful than flat files. Most RDBMSs provide database access over networks.

Software

Software originally based on a flat file database structure included FileMaker, Berkeley DB, and Borland Reflex. Popular modern relational database systems include Oracle, MySQL and PostgreSQL.

Don't Miss

Filter:
  • All types
  • Articles
  • Slideshows
  • Videos
Sort:
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the eHow.co.uk site, you consent to the use of cookies. For more information, please see our Cookie policy.