![]() ![]() ![]() Here, the point I found difficult is that once you’ve created physical model and renamed the FK fields once, you seem to have no choice but to keep repeating the same over and over again as I couldn’t find an easy way to add a table or attribute in logical and then have this incremental change syncronised into physical. This is where I think ErWin does a better job keeping the fields for FK constrainst columns in its logical layer, as it is possible to keep using the logical as your primary source of analysis, aligning it to physical and making sure the changes you make in the logical model are easily reflected into the physical. Read along to find out why they are so important. The backbone of any relational database is the primary and foreign keys. The tables are linked with one another to create connections between the data. All data is entered into tables, the so-called relations. Conceptual does not have attributes and only core entities and relationships and is there for ultra high level view where logical is not very far away from the actual implementation, although still platform agnostic Martyna Sawiska keys Relational databases organize data in a standardized manner. But the sole purpose of one designing the logical model is to facilitate the successful implementation of the physical model or models.Īlso the definition of a conceptual model is different from the one of the logical. Yes logical models are intended for the business stakeholders discussions, fair enough.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |