Human beings involved with AdventureWorks: employees, customer contacts, and vendor contacts.

Package Physical datamodel example
Author Bert Dingemans
Alias --
Stereotypes table


Name Type Cardinality Description
BusinessEntityID int 1 - 1Primary key for Person records.
PersonType nchar 1 - 1Primary type of person: SC = Store Contact, IN = Individual (retail) customer, SP = Sales person, EM = Employee (non-sales), VC = Vendor contact, GC = General contact
NameStyle bit 1 - 10 = The data in FirstName and LastName are stored in western style (first name, last name) order. 1 = Eastern style (last name, first name) order.
Title nvarchar 1 - 1A courtesy title. For example, Mr. or Ms.
FirstName nvarchar 1 - 1First name of the person.
MiddleName nvarchar 1 - 1Middle name or middle initial of the person.
LastName nvarchar 1 - 1Last name of the person.
Suffix nvarchar 1 - 1Surname suffix. For example, Sr. or Jr.
EmailPromotion int 1 - 10 = Contact does not wish to receive e-mail promotions, 1 = Contact does wish to receive e-mail promotions from AdventureWorks, 2 = Contact does wish to receive e-mail promotions from AdventureWorks and selected partners.
AdditionalContactInfo xml 1 - 1Additional contact information about the person stored in xml format.
Demographics xml 1 - 1Personal information such as hobbies, and income collected from online shoppers. Used for sales analysis.
rowguid uniqueidentifier 1 - 1ROWGUIDCOL number uniquely identifying the record. Used to support a merge replication sample.
ModifiedDate datetime 1 - 1Date and time the record was last updated.


NameSourceSource attributeTargetTarget attribute
BusinessEntityID PersonBusinessEntityIDPersonBusinessEntityID
PersonType PersonPersonTypePersonPersonType
NameStyle PersonNameStylePersonNameStyle
Title PersonTitlePersonTitle
FirstName PersonFirstNamePersonFirstName
MiddleName PersonMiddleNamePersonMiddleName
LastName PersonLastNamePersonLastName
Suffix PersonSuffixPersonSuffix
EmailPromotion PersonEmailPromotionPersonEmailPromotion
AdditionalContactInfo PersonAdditionalContactInfoPersonAdditionalContactInfo
Demographics PersonDemographicsPersonDemographics
rowguid PersonrowguidPersonrowguid
ModifiedDate PersonModifiedDatePersonModifiedDate


Import Adventureworks Database


Physical example project

Physical data model for the TFG Academy example. It shows a subset of the tables as they are included in the TFG Academy database. These three entities are used and expanded in the other two layers logically and conceptually.

Data Mapping

Data mapping is an example diagram of a data mapping in the IDEA implementation This implementation can be used in for example an ETL process but also for documenting the data flows and transformations in message transformation process or component.

Data modeling overview example

This diagram shows the associations via traces over the three modeling layers. It is thus an overview for the data modeling.