Difference between revisions of "Logical Database Design"
(Created page with "'''Content Coming Soon'''") |
m |
||
Line 1: | Line 1: | ||
− | + | == What is a Logical Database Design? == | |
+ | A logical database design is a design of a database that is based on the rules and concepts of a particular data model.<ref>[https://en.wikipedia.org/wiki/Logical_schema Logical schema]</ref> | ||
+ | |||
+ | A logical database design is independent of any physical implementation. It can be thought of as a blueprint for a database. | ||
+ | |||
+ | A logical database design is typically created by data modelers and database administrators. It includes a description of the data to be stored in the database, as well as the relationships between the data. | ||
+ | |||
+ | A logical database design is used for a number of purposes, including: | ||
+ | *To understand the data that will be stored in a database | ||
+ | *To ensure the accuracy and consistency of the data | ||
+ | *To create a design that can be easily translated into a physical database design | ||
+ | *To document the design of a database | ||
+ | |||
+ | A logical database design is an important step in the process of designing a database. It can help ensure that the data in the database is accurate and consistent and that the design can be easily translated into a physical database design. | ||
+ | |||
+ | A logical database design is important because it can help ensure that the data in a database is consistent and accurate. It can also help make sure that the database can be easily understood and maintained.<ref>[https://homepages.uc.edu/~chundusa/databasemethodology.html Database Design Methodology Summary]</ref> | ||
+ | |||
+ | |||
+ | ==See Also== | ||
+ | *[[Database (DB)]] | ||
+ | *[[Software Development Life Cycle (SDLC)]] | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==References== | ||
+ | <references /> |
Latest revision as of 23:50, 1 December 2022
What is a Logical Database Design?
A logical database design is a design of a database that is based on the rules and concepts of a particular data model.[1]
A logical database design is independent of any physical implementation. It can be thought of as a blueprint for a database.
A logical database design is typically created by data modelers and database administrators. It includes a description of the data to be stored in the database, as well as the relationships between the data.
A logical database design is used for a number of purposes, including:
- To understand the data that will be stored in a database
- To ensure the accuracy and consistency of the data
- To create a design that can be easily translated into a physical database design
- To document the design of a database
A logical database design is an important step in the process of designing a database. It can help ensure that the data in the database is accurate and consistent and that the design can be easily translated into a physical database design.
A logical database design is important because it can help ensure that the data in a database is consistent and accurate. It can also help make sure that the database can be easily understood and maintained.[2]
See Also