We are independent & ad-supported. We may earn a commission for purchases made through our links.

Advertiser Disclosure

Our website is an independent, advertising-supported platform. We provide our content free of charge to our readers, and to keep it that way, we rely on revenue generated through advertisements and affiliate partnerships. This means that when you click on certain links on our site and make a purchase, we may earn a commission. Learn more.

How We Make Money

We sustain our operations through affiliate commissions and advertising. If you click on an affiliate link and make a purchase, we may receive a commission from the merchant at no additional cost to you. We also display advertisements on our website, which help generate revenue to support our work and keep our content free for readers. Our editorial team operates independently from our advertising and affiliate partnerships to ensure that our content remains unbiased and focused on providing you with the best information and recommendations based on thorough research and honest evaluations. To remain transparent, we’ve provided a list of our current affiliate partners here.

What Is a Logical Data Model?

By Alex Newth
Updated May 16, 2024
Our promise to you
EasyTechJunkie is dedicated to creating trustworthy, high-quality content that always prioritizes transparency, integrity, and inclusivity above all else. Our ensure that our content creation and review process includes rigorous fact-checking, evidence-based, and continual updates to ensure accuracy and reliability.

Our Promise to you

Founded in 2002, our company has been a trusted resource for readers seeking informative and engaging content. Our dedication to quality remains unwavering—and will never change. We follow a strict editorial policy, ensuring that our content is authored by highly qualified professionals and edited by subject matter experts. This guarantees that everything we publish is objective, accurate, and trustworthy.

Over the years, we've refined our approach to cover a wide range of topics, providing readers with reliable and practical advice to enhance their knowledge and skills. That's why millions of readers turn to us each year. Join us in celebrating the joy of learning, guided by standards you can trust.

Editorial Standards

At EasyTechJunkie, we are committed to creating content that you can trust. Our editorial process is designed to ensure that every piece of content we publish is accurate, reliable, and informative.

Our team of experienced writers and editors follows a strict set of guidelines to ensure the highest quality content. We conduct thorough research, fact-check all information, and rely on credible sources to back up our claims. Our content is reviewed by subject matter experts to ensure accuracy and clarity.

We believe in transparency and maintain editorial independence from our advertisers. Our team does not receive direct compensation from advertisers, allowing us to create unbiased content that prioritizes your interests.

In systems engineering and database development, creating a logical data model (LDM) is the second step in creating the entire data model, coming after the conceptual data model (CDM) and proceeded by the physical data model (PDM). In the logical data model, engineers target the important data for the business and show the entire database’s relationship from one section to another. The LDM diagram will show different tables with data titles, but the actual data will not be present. For example, if a date table is made, the LDM diagram will show titles such as “Month” and “Year,” but the actual month and year values will not be present.

When it comes to data mapping, the first model is the CDM. This diagram is a simple concept that starts off the data modeling. There will be several tables, without any titles in them, and there may be some lines to show relationships.

After the conceptual model, the logical data model is made. This model is much more detailed in terms of both titles and relationships. The blank tables are filled with arbitrary values so engineers know what data is important. For example, the conceptual model will have a table named “Store,” while the LDM will fill the table with titles such as “Store Description” and “Store Name.” The data is not implemented at this stage, which intends only to let the engineers know what information is required for a functioning database.

The relationships between the different tables also are detailed, so engineers will know how to make them interact. There is usually one central table, to which all other tables connect. Between the ancillary tables, there are sometimes interconnections, showing that these tables cannot function independently of one another. Lines connecting one table to another show these relationships.

A logical data model is needed for many reasons. It clarifies what information the business is collecting and how all the data are related. This also makes it easier for management to look through the draft and see if more information is needed. The information is diagramed, so the engineers will need less time to create the data model, because the plan is detailed and there is no guesswork.

After the logical data model, the PDM is created. This is the real and physical implementation of the database. In this model, all the arbitrary values are filled with real values, such as “Year” being filled with “2011,” and the data are actually used and being collected.

EasyTechJunkie is dedicated to providing accurate and trustworthy information. We carefully select reputable sources and employ a rigorous fact-checking process to maintain the highest standards. To learn more about our commitment to accuracy, read our editorial process.

Discussion Comments

By nony — On Dec 27, 2011

@Mammmood - I’ve never seen a conceptual data model myself. I guess the manager does this before the project is handed off to me. I think if the project goes awry they will point to the conceptual data model first to make sure everything is set up correctly.

Then they will look at the logical data model. I believe these two models serve as a blueprint for the database. You certainly can’t build a solid structure without a blueprint of some kind.

By Mammmood — On Dec 26, 2011

@David09 - I totally agree. I started out with Microsoft Access and didn’t do my models correctly at first.

I didn’t even build proper relationships like I knew I was supposed to (and Access makes building and documenting relationships easy) and my database was a mess. It had lots of data integrity issues and was not streamlined in any way.

Now, I always plan out and model my data, even if it means a delay in development. It pays off down the road.

By David09 — On Dec 25, 2011

I am a firm believer in data modeling before building the database. There really is no excuse not to do it, since there are so many data modeling tools that you have at your disposal which can assist you with the process.

However, the reality is that many novice database developers skip this very important step. How do I know this? Because I was one such novice database developer myself, and I found modeling to be boring and a waste of time (so I thought) in the same way that many programmers don’t flow chart their code even though they know they should. Programmers want to dive into the “fun” stuff.

However, let me tell you what’s not fun. Months later when your database is a mess because you didn’t properly model the data, that’s not fun. Often you have to start over. Why not model it from the beginning and save yourself the hassle?

EasyTechJunkie, in your inbox

Our latest articles, guides, and more, delivered daily.

EasyTechJunkie, in your inbox

Our latest articles, guides, and more, delivered daily.