Since we are using a RDBMS our data can be accessed in a variety of different ways. My recommendation is that we keep our system as it currently configured. This would not be possible in a flat file system. In our system we need to restrict the level of access on a per flight basis. A user who has access to the file has access to all of the records. Only file level restrictions can be applied in this type of configuration. ![]() Data SecurityÄata housed within flat file systems is hard to restrict. Who would have access and how would we control it is the last disadvantage I would like to expand upon. There would need to be multiple users accessing the data to process the amount of updates we would generate. The same process would need to be applied for airport and carrier data. This is just one use case where updates could be difficult. Even with an automated update script it would be a time consuming and error-prone process. That would me traversing the entire data file and updating the last service date. When and aircraft is serviced we will need to update every instance of that aircraft within the flat file. In the case of an airccraft we keep track of the last service date. Imgaine when an update needs to be made to a piece of data. Update DifficultyĪs was mentioned in the last section there is a lot of duplicate data in the flat file. This leads us into the next disadvantage, difficulty updating records. The same is true for aircraft and carrier data. This duplication does not exsist in our RDBMS because the airport data is only stored once. Not only is the originating airports data duplicated, the aircraft data is also duplicated for every flight on that days route. This data duplication causes the size of the flat file system to increase with unnecessary data. Each record includes the data about that airport. In the example data extract shown above records 1 and 2 have flights orignating from the MIA airport. These include data duplication, difficulty of updating, and data security. There are several disadvangtes to using a flat file system for our data. While a flat file based system can work for some datasets I do not think it is appropriate for us. ![]() Simple queries and sorting should be no problem for most flat file based systems. Users will also have very little difficulty with understanding the data because each record contains all available about a given flight. A flat file system can be viewed from any number of applications making is very accessible. The second advantage we will examine is the ease of use for the database. This setup makes the data very readable and understandle to anyone who has access to the file. This means that all the data available is within any given record. One of the main advantages of a flat file based system is having all of the available data in the same location. Two of the main advantages of a flat file system are the simplicity of record storage and the ease of use of the data. I know from the last few staff meetings that we are looking to change our database configuration from a traditional relational database mangement system (RDBMS) to a flat file storage based system. Be sure to think critically, and include any problematic use case scenarios." Include the pros and cons of the relational database format and the flat file format. Write your boss a memo, outlining any concerns or hesitations you have about moving to this format for management of your data. ![]() "You have some concerns about moving your entire airline operations out of SQL to this flat file format. My latest assignment for my Data Visualizations class give me this case, Flat File vs Relational Database System Assignment Home Subscribe Flat File vs Relational Database System Assignment 22 February 2016 on show_your_work, data visualizations, RDBMS, Flat File Data System
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |