Logical/Physical Views

We are glad you created this "Idea" ticket. We will discuss it with our team and work on it, in case there are lot of user votes for this.

Thank you for your assistance,

SqlDBM Team

Did these features get implemented? Logical/Physical views are very important aspects of data modeling. Also, abbreviation glossary is important in organizations which have matured data governance and standards practice.

It should be noted here that the difference between logical and physical models is not just as simple as having different names / labels for items. In the logical model, we display content logically, in business terms. How that is physically modelled, can be quite different. In other words, we might logically describe a customer in the logical, but in the physical model, we might split Customer out into Applicant, Lead, Qualified Lead...etc. One table in the logical might result in numerous tables in the physical. Another example would be the implementation of a party reference model in the physical, that is a completely different implementation to the logical.

So...what we actually need, is the ability to define Conceptual, Logical and Physical models, and to provide TRACEABILITY from the conceptual, to the logical and the physical. So that we can say, this physical model is an instantiation of this logical model. Going deeper, we should be able to even link entities and attributes from the higher level to the lower level.

SQLDBM is a great tool for designing the physical data model. I am using it extensively, but in order for me to use it more readily in large scale enterprises, I would need this feature to facilite true enterprise data modelling.

Is this implemented ? Do we have this feature ?

Yes, this feature is available for the Business Plan. Please see the screenshots how to start using it as well as Naming Conventions. 

Also read the article on it https://blog.sqldbm.com/naming-conventions/

Best, 

Team SqlDBM