Frequently-Asked Questions
Database design is the process of creating logical and physical data models to govern a database system. The goal of database design is to ensure the accuracy and comprehensiveness of the information contained in a data asset while also avoiding redundancy and other inefficiencies. A well-designed database allows organizations to easily find, access, and retrieve information whenever needed, eliminating waste and saving time.
In short, a physical data model is the database representation of a logical data model. A logical data model is a communication tool used to “translate” between business needs and database design, using concepts and terms that business analysts without technical backgrounds can understand. A physical data model is the expression of the logical data model in the data asset design. A physical data model includes tables, columns, keys, validation rules, domains, and access constraints. A logical model uses entities, relationships, and attributes to describe what the physical data model should do.
Data normalization is essentially the process of organizing and “cleaning up” data in order to ensure users can properly utilize a data asset for queries and analysis. Normalization involves eliminating redundancies, logically grouping data to make it easier to find related data assets, and resolving conflicting data. Data normalization is critical to ensuring a data asset can be used easily and successfully.