You’ll end up with everybody overwriting everybody else’s changes. ![]() How about 10 at the same time or 100 people at the same time?. How about having more than one person overwriting the same data at the same time. And it’s unacceptable to lose important data like orders of a customer, allergies of a patient, flight bookings, …etc. “What if you had a disconnect or a crash, and you lost your data?”. If the redundant data (having multiple copies of the same data) will lead to conflict, you would need to have only non-repeated unique data. In addition, “Do you need to know who made every change at every point?”. ![]() ![]() If the data is sensitive, and you need to restrict access to the data It doesn’t need to be shared with everyone. If yes, nothing could actually prevent me from typing incorrect data into a spreadsheet. “Do you care if someone entered incorrect data?”. You may have thousands or millions of rows of customers, or any piece of information. Consider the following potential problems: Size This takes us to the next question, “ When do we actually need a database?”. What if you have a bunch of data, maybe 10,000 customers, “ Are you going to scroll down in the spreadsheet to get the 9999 customers?!”, What if the security was a concern, “ Do you care about if someone else got access to your data?”, What if you accidentally put redundant information, “ Is it fine to have duplicate information along with the spreadsheet?”. The problem is what comes next, and there’s a lot of potential problems. ![]() That might be OK, because just having data is not a good enough reason to need a database, and it’s not the problem. Now, we have a kind of data, and you stored them in spreadsheets in a way that satisfies your need. Probably this is what comes into your mind when you hear the term “database”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |