Simple systems can easily contain basic information for a quick database. Continued Useįlat file databases do have some uses, even though the functionality of this data model is not quite as efficient as a faster, relational approach. This means that someone can use the system to more easily find all of the information for a customer, including total order history. Each of these tables include fields that connect them to each other. Another person can then enter information for his or her order in a separate table. When the customer calls to place an order, someone enters his or her information in a 'customer' table within the database.

The same customer example given above might look quite different in a relational model. Multiple tables become connected through these fields, allowing each one to have only part of the total information needed. This model allows information in one table to be related to other tables using key fields which exist in each one. The common database used today is a relational database.

Since each record needs to be complete in and of itself, a flat file system usually results in very large files or a lack of connectivity between information within it. These files are not related in any way, so someone using a flat file database to find customer information can easily miss additional files about orders. Information about an order stored in one flat file is not associated with information about the customer stored in a different one. This is not necessary, however, so multiple files could be maintained: one for the customer, and one for each individual order. A flat file system might store all of this information for the customer in a single file. That same person, or someone else, then enters information for that particular order. Would you please help me in comparing the two files? Will it be feasible in Java since the file size will be huge?.If a customer calls a business to place an order, then someone enters his or her information into a table or database. Detail data ordering will be same in both the files.ĭesired output : For Key 54321, Data(pos 13:19) is not same. These claims can be present randomly in the other file.Its not line to line mapping. The file format is - one header and claim data(12345) in one line and its detail data can be more than one.

I will need to compare the two files based on their mapping.

This is a sample file and may size upto 500mb and about 50 fields. Mapping for both file will be same: Header:

Flat file comparison tool