Physical schema (original) (raw)
A physical data model (or database design) is a representation of a data design as implemented, or intended to be implemented, in a 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 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.
| Property | Value |
|---|---|
| dbo:abstract | A physical data model (or database design) is a representation of a data design as implemented, or intended to be implemented, in a 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 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. As of 2012 seven main databases dominate the commercial marketplace: Informix, Oracle, Postgres, SQL Server, Sybase, IBM 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 (Starting with SQL Server 2017, SQL Server runs on Linux. It's the same SQL Server database engine, with many similar features and services regardless of your operating system), 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. (en) |
| dbo:thumbnail | wiki-commons:Special:FilePath/Physical_Data_Model_Options.jpg?width=300 |
| dbo:wikiPageExternalLink | https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/fea_docs/FEA_CRM_v23_Final_Oct_2007_Revised.pdf |
| dbo:wikiPageID | 1030540 (xsd:integer) |
| dbo:wikiPageInterLanguageLink | dbpedia-ja:スキーマ_(データベース) |
| dbo:wikiPageLength | 4724 (xsd:nonNegativeInteger) |
| dbo:wikiPageRevisionID | 1084726696 (xsd:integer) |
| dbo:wikiPageWikiLink | dbr:Index_(database) dbr:MySQL dbr:Conceptual_schema dbr:Partition_(database) dbr:Data dbr:Data_management dbr:Database_administrator dbr:Database_design dbr:Database_schema dbr:Logical_schema dbr:Data_cluster dbr:Database dbr:Database_management_system dbc:Data_modeling dbr:Relational_database dbr:ANSI-SPARC_Architecture dbc:Data_management dbr:Sybase dbr:PostgreSQL dbr:IBM_Db2 dbr:Microsoft_SQL_Server dbr:Microsoft_Windows dbr:Operating_system dbr:Oracle_Database dbr:XML dbr:Conceptual_data_model dbr:Logical_data_model dbr:Three_schema_approach dbr:Reverse-engineer dbr:Secondary_storage dbr:Project_lifecycle dbr:Informix_Dynamic_Server dbr:Database_artifact dbr:File:Physical_Data_Model_Options.jpg |
| dbp:wikiPageUsesTemplate | dbt:As_of dbt:Citation_needed dbt:Refimprove dbt:Reflist dbt:Short_description dbt:Unreferenced_section |
| dct:subject | dbc:Data_modeling dbc:Data_management |
| gold:hypernym | dbr:Term |
| rdfs:comment | A physical data model (or database design) is a representation of a data design as implemented, or intended to be implemented, in a 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 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. (en) |
| rdfs:label | Physical schema (en) |
| owl:sameAs | freebase:Physical schema wikidata:Physical schema https://global.dbpedia.org/id/fUyM |
| prov:wasDerivedFrom | wikipedia-en:Physical_schema?oldid=1084726696&ns=0 |
| foaf:depiction | wiki-commons:Special:FilePath/Physical_Data_Model_Options.jpg |
| foaf:isPrimaryTopicOf | wikipedia-en:Physical_schema |
| is dbo:wikiPageRedirects of | dbr:Physical_data_model dbr:Physical_schema_(version_2) |
| is dbo:wikiPageWikiLink of | dbr:Physical_data_model dbr:Data_modeling dbr:Physical_schema_(version_2) |
| is foaf:primaryTopic of | wikipedia-en:Physical_schema |
