 thumb|320px|physical data model options.[http://georgewbush-whitehouse.archives.gov/omb/egov/documents/crm.pdf fea consolidated reference model document]. whitehouse.gov may 2005. p.91. a physical data model (or database design) is a representation of a data design which takes into account the facilities and constraints of a given database management system. in the  lifecycle of a project it typically derives from a logical data model, though it may be reverse-engineered from a given database implementation. a complete physical data model will include all the database artifacts required to create relationships between tables or to achieve performance goals, such as indexes, constraint definitions, linking tables, partitioned tables or clusters. analysts can usually use a physical data model to calculate storage estimates; it may include specific storage allocation details for a given database system.  seven main databases dominate the commercial marketplace: informix, oracle, postgres, sql server, sybase, db2 and mysql. other rdbms systems tend either to be legacy databases or used within academia such as universities or further education colleges. physical data models for each implementation would differ significantly, not least due to underlying  operating-system requirements that may sit underneath them. for example: sql server runs only on microsoft windows operating-systems, while oracle and mysql can run on solaris, linux and other unix-based operating-systems as well as on windows. this means that the disk requirements, security requirements and many other aspects of a physical data model will be influenced by the rdbms that a database administrator (or an organization) chooses to use. ==references==    fea consolidated reference model document (whitehouse.gov) oct 2007.
Data_modeling