To achieve this, the database designer must know in advance what the data is going to represent, how is it going to be acquired and at what rate, what its operational volume will be (i.e., how much data is expected), and, finally, how it is going to be used.įor example, an industrial information system where data is gathered manually every day will not have the same data model as an industrial system where information is generated in real time. 1: Ignoring the Purpose of the Dataĭata is stored to be consumed later, and the goal is always to store it and retrieve it in the most efficient manner. ![]() In this article, you will learn about some of the common database design bad practices, why they are bad, and how you can avoid them. If you are an experienced developer, chances are you will also notice bad database design examples-things that could have been done better in the beginning, if only someone had given you some database design tips. ![]() And, once they do, you start noticing many ways to improve and take advantage of the stored information. ![]() You are faced normally with confusing tables, views, columns, values, stored procedures, functions, constraints, and triggers that take a long time to make sense to you. One such challenge-more often than not the most demanding one-involves understanding the data model of an application. Whenever you, as a developer, are given a task based on existing code, you have to face many challenges.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |