Blog Timeline Full Width

  • Unstructured data classwords

    Each attribute on our data model ends in a classword. For example, “Number” is the classword in Account Number, “Name” is the classword in Customer Last Name and “Date” is the classword in Order Entry Date. As we start modeling more and more unstructured data, we...

    Read more
    0
    Steve Hoberman
  • Evolutionary or revolutionary approach to modeling NoSQL?

      The symbols we use on our data models were created with relational databases in mind. Luckily, conceptual and logical data models are independent of technology so we can still use our symbols for modeling non-relational (NoSQL) databases. When we reach the physical level however, things...

    Read more
    0
    Steve Hoberman
  • Reverse Engineering a MongoDB Document

    You are the data modeler responsible for building a logical data model of an existing NoSQL MongoDB database. Your plan is to reverse engineer the existing database into a physical data model using your data modeling tool, and then translate this physical data model into a logical...

    Read more
    1
    Steve Hoberman
  • How should project teams use the Enterprise Data Model?

    There is a team of data architects that have been working on a logical enterprise data model (EDM) for three months, and the EDM is estimated to be 40% complete. Many projects are underway that can benefit from the EDM, yet the architects are divided as...

    Read more
    1
    Steve Hoberman
  • Having the same primary key in two or more logical entities

    You are a data modeler designing a data mart, and have come across at least two different entities on your logical data model that happen to have the same primary key. On your physical data model, would you keep them in separate tables or merge them...

    Read more
    0
    Steve Hoberman