Database Design vocabulary table

1. Access Method: This step includes storing and retrieving records from files.
2. Alias (alias): Another name of an attribute. In SQL, you can replace the table name with an alias.
3. Alternate keys (backup key, ER/link model): no candidate key is selected as the master key in the entity/table.
4. anomalies (exception) See Update exception (update anomalies)
5. Application Design Program Design): a stage in the lifecycle of a database application, including designing the user interface and using and processing the database application.
6. Attribute (attribute) (relational model): an attribute is a column named in a link.
7. Attribute (attribute) (ER Model): a property in an object or link.
8. Attribute inheritance: a subclass member can have its own attributes and inherit the attributes related to the superclass.
9. base table: A named table with physical records stored in the database.
10. Binary relationship: an ER term used to describe the relationship between two entities. For example, panch has staff.
11. Bottom-up approach (bottom-up method): used for database design, a design methodology that starts from identifying each design build and then aggregates these components into a large unit. In database design, you can start the underlying design from the representation attribute, and then combine these attributes to form a table that represents the object and link.
12. Business Rules: Additional Rules specified by the user or database administrator.
13. Candidate Key (Candidate Key, er relational model): contains only the superkeys of the minimum number of attributes/columns required to uniquely identify an object.
14. cardinality (base): Describes the number of possible relationships involved in each object.
15. centralized approach (centralized method for database design): a collection of requirements that each user tries to combine into a new database application
16. chasm trap: Assume that there is one object, but some entities do not have a path.
17. Client: a software application that requests services from one or more servers.
18. Clustering field: records the total number of non-key fields used for cluster (SET) flight records. These rows have the same value on this field.
19. clustering index: The index defined on the cluster field of the file. A file can have at most one primary index or one cluster index.
20. Column: attribute ).
21. complex relationship (complex relationship): relationship with a degree greater than 2.
22. Composite attribute: an attribute composed of multiple simple components.
23. composite key (composite key): The primary key that contains multiple columns.
24. Concurrency Control (Concurrency Control): a dbms service that executes multiple 15-15 times in a multi-user environment and ensures data integrity.
25. constraint (constraints): the database does not allow consistency rules that contain erroneous data.
26. data conversion and loading (data conversion and loading): a stage in which the lifecycle of a database application is heavy, this includes converting existing data to a new database, and converting the application in the sauce to a new database.
27. Data Dictionary (data dictionary): see system directory (system Catalog ).
28. Data independence (Data independence): Data Description section of the application that uses data. This means that if a new data structure is added to the database or the existing structure in the database is modified, the use of this database will be affected, unless the application is not directly dependent on the modified part.
29. Data Model: an integrated set that describes the concepts of data, inter-data relationships, and data constraints.
30. data redundancy (data redundancy): see redundant data (redundant data ).
31. Data Security: including access and use of database objects (such as tables and views) and operations that users can perform on these objects.
32. Database: a collection of logically related data (and the description of the data), used to meet the company's information requirements.
33. Database Design: a stage in the lifecycle of a database application, including creating a database that supports the company's operations and objectives.
34. database integrity: indicates the correctness and consistency of the stored data. Integrity is usually expressed by constraints.
35. Database Management System, DBMS (database management system): a software system that allows users to define, create, and maintain databases and control database access.
36. Database Planning (Database Planning): it can implement management activities at various stages of database applications as effectively as possible.
37. Database Server: Same server.
38. DBMS engine (DBMS engine): Same server.
39. DBMS Selection: a stage in the lifecycle of a database application, including selecting an appropriate DBMS to support database applications.
40. Degree of a relationship: number of entities involved in a link.
41. denormalization: In form, This term refers to the modification of the basic table structure, so that the new table is less normalized than the original table. However, it can also be used to describe the situation of combining two tables into a new table, which has the same paradigm as the original table, but it contains more null values than the original table.
42. derived attribute (derived attribute): indicates the attribute whose value can be derived from the value of a related attribute and attribute set. This attribute is not required in the object.
43. Design Methodology (Design Methodology): a structured approach that uses processes, tools, and documents to support and simplify design processes.
44. disjoint constraint (no join constraint): describes the relationship between sub-class members and determines whether a member of a super class may become a member of one or more sub-classes.
45. domain: the value range of one or more attributes.
46. Entity (entity): a collection of objects of the same nature, which are identified by users or companies and can exist independently.
47. entity Integrity: In a basic table, the value of the primary key column cannot be empty.
48. entity occurrence (entity appearance): a unique and identifiable object in the entity.
49. entity-relationship model: detailed logical representation of the company's entities, attributes, and relationships.
50. Fact-finding (fact discovery): uses techniques such as interviews and questions to collect formal processes on system facts, requirements, and performance.
51. fan trap: but the two entities that fan out of the third entity have a 1: * relationship, however, these two entities should have a direct relationship between them to provide necessary information.
52. Field: Same as the Meta Group (tuple ).
53. File: A name set of related records stored in the sub-primary storage.
54. file-Based System (file-based system): a collection of files used to manage (create, insert, delete, update, and retrieve) data in one or more files, and generate applications (usually reports) based on the data in these files ).
55. file organization: the arrangement of records in files when files are stored on disks.
56. First Normal Form (1nf, first paradigm): The intersection of each column in the table and the record contains a table that contains a value.
57. Foreign key (foreign key): a set of one or more columns in a table. These columns match the candidate keys in some (or possibly the same) tables.
58. 4gl, fourth-generation language (fourth-generation language): A non-procedural language, such as SQL, which only requires you to define what operations must be done, 4gl is responsible for translating the operations into how to implement these operations.
59. Full functional dependency (full function dependency): A column is functionally dependent on the composite primary key, but not on any subset of the primary key.
60. functional dependency (function dependency): describes the relationship between columns in the table.
61. generalization (generalization): The process of minimizing the differences between entities by identifying common features between entities.
62. generalization hierarchy (generalized hierarchy): Hierarchy of the same type ).
63. Global Data Model: A data model that represents the entire company (and a part of the modeled company.
64. Implementation (Implementation): a stage in the database application lifecycle, including physical implementation of database and application design.
65. Index: a data structure that allows DBMS to place a specific record in a file more quickly, thus accelerating the response to user queries.
66. Infomation System: resources that can collect, manage, control, and distribute data/information across the company.
67. Inheritance (inheritance): see attribute inheritance ).
68. Integrity constaints: prevents data inconsistency constraints in the database.
69. IS-A hierarchy (IS-A hierarchy): type hierarchy ).
70. Local Logical Data Model (local Logical Data Model): a data model that represents a combination of a specific user view or user view.
71. logical database design (logical database design): the process of building a company's data model based on a specific data model, but does not rely on specific DBMS and other physical conditions.
72. Meta-data (metadata): For data, see system directory ).
73. Mision objective: identifies specific tasks that must be supported by the database.
74. Mission Statement (mission statement): defines the main objectives of database applications.
75. Multiplicity (diversity): defines the number of occurrences of entities associated with one occurrence of a related entity.
76. multi-valued attribute (multi-value attribute): an attribute that stores multiple values for an object.
77. nonkey attribute/column (non-key attribute/column): attribute/column that is not part of the key.
78. Normal Forms (paradigm): a stage of the standardization process. The first three paradigms are 1nf, 2nf, and 3nf respectively ).
79. normalization (normalization): a technology that produces features that meet the needs of users and companies.
80. null (null value): the value of a column that is unknown or unavailable for this record.
81. operational maintenance (Operation Maintenance): a stage of the database application life cycle, including monitoring and maintaining the running of the system after installation.
82. Participates in the constraint (EER model): determines whether each occurrence of a superclass must be involved as a member of the subclass.
83. Participation constraint (ER Model): determines whether all or only some entities are involved in the link.
84. physical Database Design (physical database design): the process of generating A description of the database implementation on the secondary storage, it describes the basic tables, the organization of files, the indexes used for obtaining valid access, and all descriptions related to integrity constraints and security restrictions.
85. Primary Index (Primary Index): Index built on the sorted key field of the file. A file can have at most one primary index or one cluster index.
86. Primary Key (master key, ER Model): used to identify candidate keys for each entity.
87. Primary Key (master key, relational model): used to identify the candidate key for record uniqueness in a table.
88. Privileges: allows you to perform operations on a given basic table and view.
89. prototyping: a stage of the application lifecycle of a database, including the workflow model of the database application.
90. query-by-example (QBE): A non-procedural database language for relational DBMS. QBE is a graphical "point-by" Method for querying databases.
91. RDBMS: relational DBMS.
92. Record: Same as the metadata group (tuple ).
93. Recovery control: At that time, Pepsi restored the database to the correct state.
94. rcursive relationship: a link that prevents the same entity from participating in multiple times in different roles. For example, staff supervises staff.
95. redundant data (redundant data): duplicate data stored in multiple tables.
96. referential integrity (reference integrity): If a table has a foreign key, the foreign key value must match the value of the candidate key of some records in the master table.
97. Relation: a relational table also has columns and rows.
98. relational model: a data model that represents data in the form of tables (or relationships.
99. Relational Database (Relational Database): a set of standardized tables.
100. Relation: a meaningful relationship between entities.
101. Relationship occurrence: a uniquely identifiable link between two entities.
102. requirements collection and analysis: a stage of the database application lifecycle, including collecting and analyzing company information to be supported by database applications, this information is used to identify new database application requirements.
103. Row (ROW): Same as the metagroup (tuple ).
104. Second Normal Form (second paradigm): a table that is already in the first paradigm, and satisfying all non-primary key columns can only be obtained from all the columns that constitute the primary key.
105. Secondary index (secondary index): The index defined on the non-Ordered Field of the data file.
106. Security: prevents unauthorized database users from accessing the database, including intentionally or unintentionally. RDBMS usually provides two types of security: data security and system security.
107. SERVER: the software application that provides services to the requesting customer. See the two-tier/three-tier client-server architecture.
108. Simple attribute: only one component attribute.
109. single-valued attribute (single-Value Attribute): an attribute with only one value for an object.
110. Specialization (special): identifies the process of distinguishing features of members between entities to maximize the differences between members of entities.
111. Specialization hierarchy: type hierarchy ).
112. Structured Query Language (Structured Query Language): A non-procedural database language for RDBMS. In other words, you only need to specify the information you need, instead of how to obtain the information. SQL has been standardized by the International Organization for Standardization (ISO). Therefore, SQL is the formal and actual standard language for defining and manipulating RDBMS.
113. Strong entity (strong entity): An entity that does not depend on the existence of the primary keys of other entities.
114. subclass (subclass): An entity that appears in a (superclass) object and maintains specific attributes and relationships with different roles.
115. superclass. For more information, see special and general.
116. superkey (superkey, ER Model): an attribute or attribute set, which identifies the appearance of each entity.
117. superkey (superkey, relational model): a column or column set uniquely identifies a record in a table.
118. System catalog (system directory): stores data about the database structure, user, application, and other information.
119. system definition: a stage in which the database application declares a heavy cycle, including defining the database application and its main user views and boundaries.
120. System Security (System Security): It is inferior to the user name and password to protect the access and use of databases at the system level.
121. Table: relation ).
122. Ternary relationship (ternary relationship): Relationship between three entities. For example, the registers relationship between panch, staff, and member.
123. Testing: a stage of the database application lifecycle, including executing the application and intentionally discovering errors.
124. third normal form, 3nf (third paradigm): a table that already has 1nf and 2nf, and the values of all non-primary columns can only be obtained from the primary key column, it cannot be obtained from other columns.
125. 3gl, third-generation language (third-generation language): A Procedural language, such as COBOL, C, C ++, which requires users (usually programmers) specify what must be done and how to do these tasks.
126. three-tier client-server architecture (three-tier client-server architecture): a client that processes user interfaces, application servers that process business logic, and data processing, the database server is used to run DBMS.
127. top-down approach (top-down method for database design): A design method that begins with defining the main structure of the system, then, these structures are gradually subdivided into smaller units. In the database design, start the top-level step by identifying the relationship between the object and the data, and then gradually add details, such as the information about the object and the link you want to save (as an attribute) and all constraints on entities, relationships, and attributes.
128. Transaction: an action or a series of actions executed by users and applications to access or modify the database content.
129. Transaction Processing monitor, TPM (Transaction Processing monitor): a program that controls data key conversion between the client and the server to provide a consistent environment for online transaction processing (OLTP.
130. transitive dependency: Assume that A, B, and C are columns in the table. If B depends on a (A --> B ), and C depends on B (B --> C), C passes through B and depends on a (assuming a does not depend on B or C ). If a transfer dependency exists on the primary key, this table is not 3nf. Dependencies must be removed from the table to meet the 3nf requirement.
131. tuple (tuples): a record in a link.
132. two-tier client-server architecture (two-tier client-server architecture ): it is composed of the main business and data processing logic, the client applications that work with user interfaces, and the server programs that manage and control database access.
133. type hierarchy (type hierarchy): one is to mention its sub-classes and their superclasses, and so on.
134. UML (Unified Modeling Language): a new method that introduced many Object-Oriented Analysis and Design Methods in 1980s and 1990s.
135. Update anomalies (update exception): When the user view updates an identifier containing redundant data, it may cause inconsistency. There are three types of exceptions: insert, delete, and update.
136. User View: The requirements for database applications defined from the perspective of specific jobs (such as managers or managers) or business application areas (such as marketing, staff, or inventory control.
137. View: A "virtual base table" that does not actually exist in the database, but is generated by the DBMS from the basic table it involves.
138. View integration approach (view synthesis method, used for database design): The requirement of each user view, used to build an independent data model representing the user's attempt. In the database design stage, the result database model is merged into a larger model.