Which is better, a sequential file or a database? And, when would a database be more beneficial?

Answer 1

From 1 to 50 records a flat sequential file such as (Microsoft Excell Spreadsheet). As well as generic database software that let's you develop a (Flat) database file will also do the job for you.

If your in a business taking orders and (John Smith) orders 6 items this week and five items next week then you find that your typing his name and address over and over again. this is a waste of hard drive space.

Now lets look at (Microsoft Access) which is a relational database. and let's futher assume that you buy products and resale them over the internet. Lets also assume that you have employees, now the situation changes.

So now you find that in your business that you actually have the following:

1. Employees
2. Customers
3. Shippers
4. Products
5. Categories of your products
6. Suppliers
7. Orders coming in
8. and details about the orders

Now a flat sequential file you have to type the same information over and over again.

In a relation database (Microsoft Access) you setup one table and you name it (Employees) these employees take orders either by phone or via the internet so you make a nother table called (Orders) in the relational database you setup a relationship from the employee table to the orders table. In other words (One employee can take many orders.)

This is called a relationship and more specifically, it called,
One to Many (meaning this employee can take many orders.)

On the other hand your company will have customers, and these customers can place many orders. So now your employee can take many orders from one customer. So there has to be a relationship betweer the Employee, The Customer, and the order.

To cut this explination a little short, you also will have suppliers and one supplier can provide many products and once the order is taken then it must be shipped so you need to have a shipper's table...

So you see as a company get larger it needs a way to record just one customer name and then track all the orders from that customer and exactually what they bought.

So this is where you need a relational database program.

I hope this is not to confusing.

Hope this helps

Sparky Miller
Wellsville, Ohio

Answer 2

Sequential Database

Answer 3

A database is a set of sequential files of some format. So you decide which one is better.

As for beneficial, it really depends on your needs. If you have a few records and some tables, then a simple file will usually do, except that, of course you will need to worry about the file access, writing, ettc. However, writing your own "database" routines can be time consuming and unsafe. So usually it is better to go with a tried and tested solution and use an exisitng database API (which will of course use its own file formats) . This will not only make the development faster, but it will also reduce the probability of data corruption. Then again, this method will increase the dependecy set of your project and make the final application larger.

Answer 4

With the simple file, you will have to completely understand where each field begins and ends. It would be a bit difficult to later change the size of the fields. With a database, even a simple one such as access, you don't worry about how the data is stored. The database manages it entirely. All you do is call up the records and access the fields. Unless you plan to add indexing to your file, looking up records by keys could be difficult or slow. Also, databases are less likely to become corrupt if interrupted during a write because the database engine will cancel the non-completed write, whereas a flat file could easily become corrupt.

Very few applications use simple files anymore, unless it is just for things like settings, and mlsc. stuff.

Answer 5

So put this way: is roll-out-your-own sequential file or ready-made DBMS is more beneficial?