[Database Knowledge] English database explanation __ Database

English Database Interpretation

Database Design Vocabulary Comparison
1. Access method (Access Methods): This step includes storing and retrieving records from a file.
2. Alias: Another name for a property. In SQL, you can replace the table name with an alias.
3. Alternate keys (alternate key, er/relational model): There is no candidate key in the entity/table that is selected as the primary health.
4. Anomalies (exception) See update exception (updated anomalies)
5. Application design: A phase of the database application lifecycle, including the design of user interfaces and applications that use and process databases.
6. Attribute (property) (relational model): A property is a named column in a relationship.
7. Attribute (property) (ER model): A property in an entity or relationship.
8. Attribute inheritance (property inheritance): A child class member can have its own properties and inherit the process of those attributes related to the superclass.
9. base table (Basic tables): A named table whose records are physically stored in the database.
Binary relationship (two Yuan relationship): an ER term used to describe the relationship between two entities. For example, Panch has Staff.
Bottom-up approach (bottom-up approach): For database design, a design methodology that starts with identifying each design build and then aggregates the components into a large unit. In database design, you can start the underlying design from the presentation property, These attributes are then grouped together to form a table representing entities and relationships.
Business rules (Business Rules): Additional rules specified by the user or the manager of the database.
Candidate key (candidate key, ER relational model): A super Key that contains only the minimum number of attributes/columns that are required to identify the entity.
Cardinality (Base): Describes the number of possible relationships for each participating entity.
Centralized approach (centralized method for database design): Merging each user's attempted requirements into a collection of requirements for a new database application
Chasm Trap (Deep pit traps): Suppose one exists between entities, but there is no path between some entities.
Client (clients): a software application that requests services from one or more servers.
Clustering field (Cluster field): Records any of the key Non-key fields that are used for cluster (set) navigation records, which have the same value on this field.
Clustering index (clustered index): The indexes defined on a file's cluster field. A file has at most one primary index or one cluster index.
Column (columns): Participating attributes.
Complex relationship (complex relationship): a relationship of degrees greater than 2.
Composite attribute (compound property): A property consisting of multiple simple components.
Composite key (compound key): A master that contains multiple columns.
Concurrency control: A DBMS service that performs multiple XV concurrent and guarantees data integrity in a multiuser environment.
Constraint (Constraint): The database does not allow consistency rules that contain error data.
Data conversion and loading: a phase of the database application lifecycle, including converting existing data into a new database and 耨 application conversion to a new database.
Data dictionary dictionary: See System directory (Systems catalog).
Data independence: Data Description section of an application that uses data. This means that if a new data structure is added to the database, or if the existing structure in the database is modified, the use of the database is affected, Unless the application is not directly dependent on the part being modified.
Data model: an integrated set of concepts that describe data, relationships between data, and constraints on data. Data redundancy (redundancy): see Redundant data (redundant).
Data security: Includes access to and use of database objects, such as tables and views, and actions that users can implement on those objects.
Database: A shared collection of logically related data (and the description of the data) to address the company's need for information.
Database design: A phase in the database application lifecycle, including the design of a database that supports the operations and goals of the company.
DB Integrity (Database integrity): Refers to the positive determination and consistency of the stored data. Completeness is usually expressed in constraints.
DB Management System,dbms (Database management System): A software system that enables users to define, create and maintain databases, and control access to the database.
DB Planning (Database planning): can be as effective as possible to achieve the database application of the various stages of management activities.
(Database server): Same server.
DBMS engine (DBMS engine): Same server.
DBMS selection (DBMS selection): A phase of the database application lifecycle, including selecting a suitable DBMS to support database applications.
Degree of a relationship (degree of relationship): Number of entities participating in a relationship.
Denormalization (Anti-normalization): Formally, this term refers to the modification of the base table structure, so that the new table is less normalized than the original table. But it can also be used to describe more broadly the case of putting two tables and forming a new table, This new table has the same paradigm as the original table, but contains more null values than the original table.
Derived attribute (derived property): Represents a property whose value can be derived from the value of a related property and property set, which is not required in the entity.
Design methodology: A structured approach that uses processes, tools, and documentation to support and simplify the design process.
Disjoint constraint (no connection constraint): Describes the relationship between the members of a subclass, and indicates whether a member of a superclass can become a member of one or more child classes.
Domain: The range of values for one or more properties.
Entity (Entity): A collection of objects of the same nature that are identified by a user or company and can exist independently.
Entity Integrity (Entity Integrity): In a basic table, the value of the primary health column cannot be null.
Entity occurrence (Entity presence): A uniquely identifiable object in an entity.
Entity-relationship Model: A detailed logical representation of a company's entities, attributes, and relationships.
Fact-Finding (facts found): Use techniques such as interviewing and questioning to gather the formal process of the facts, requirements, and performance of the system.
Fan Trap (fan traps): But the two entities fan out from the third entity have a fan trap when there is a 1:* relationship, but the two entities should have a direct relationship between them to provide the necessary information.
Field (fields): Same tuple (Tuple).
File: A named collection of related records stored in the secondary main storage.
file-based System (file-based systems): A collection of files that is used to manage (create, insert, delete, update, and retrieve) data in one or more files and produce applications based on the data in those files (usually reports).
File organization: How to arrange records in a file when the file is stored on disk.
First normal form (1NF): The intersection of each column in the table and the record contains a table that is tangent to the containing value.
Foreign key (external health): A column in a table or a collection of columns that match a candidate key in some other (or possibly the same) table.
4GL, Fourth-generation Language (Fourth generation language): a non-procedural language, such as SQL, he only needs the user to define what must be done, and 4GL is responsible for translating the operations into how to implement them.
Full functional dependency (complete function dependency): A column is functionally dependent on a composite master, but does not depend on the conditions of any one subset of the primary health.
Functional dependency (functional dependencies): Describes the relationships between columns in a table.
Generalization (generalization): The process of minimizing differences between entities by identifying common characteristics between entities.
Generalization hierarchy (generalization hierarchy): The same type hierarchy (kind hierarchy).
Global Data Model: A data model representing the entire company (and part of the modeled company).
Implementation (Implementation): A phase of the database application lifecycle, including the physical implementation of database and application design.
Index: A data structure that allows a DBMS to place a particular record faster in a file, thus speeding up responses to user queries.
Infomation System (Information System): the ability to collect, manage, control, and distribute data/information across a company-wide range of resources.
Inheritance (inheritance): See Property Inheritance (Attribute inheritance).
Integrity constaints (integrity constraint): Prevents inconsistent data constraints in the database.
Is-a hierarchy (is-a hierarchy): Same type hierarchy (type hierarchy).
Local logical data Model: a combination of a specific user view or user view.
Logical Database design: The process of building a model of a company's data based on a specific data model, but not on specific DBMS and other physical conditions.
Meta-data (metadata): Data about data, see System directory (Systems catalog).
Mision Objective (Mission goal): Identify specific tasks that the database must support.
Mission Statement (Mission Statement): Defines the primary goal of a database application.
Multiplicity (diversity): Defines the number of occurrences of an entity related to a single occurrence of a related entity.
Multi-valued attribute (multivalued property): A property that holds multiple values for the occurrence of an entity.
Nonkey Attribute/column (Non-key Property/column): An attribute/column that is not part of a key.
The normal forms (paradigm): a phase of the normalization process. The first three paradigms are firstly normal (1NF), second Normal (2NF), and third Normal (3NF).
Normalization (Normalization): a technology that produces features that support the needs of users and companies.
Null (null value): Represents the value of a column that is not currently known or is not available for this record. Bayi. Operational maintenance (Operation Maintenance): a phase of the database application lifecycle, including monitoring and maintaining the operation of the system after installation.
Participation constraint (Participation constraint, EER model): Determines whether each occurrence in the superclass must participate as a member of a subclass.
Participation constraint (Participation constraint, ER model): Determines whether all or just some entities are present in the relationship.
Physical Database design: The process of generating a description of a database implementation on level Two storage that describes the basic tables, the organization of the files, the indexes for effective access, and all the instructions related to integrity constraints and security restrictions.
Primary Index (primary index): The indexes built on the ordered key fields of a file. A file can have up to one primary index or one cluster index.
Primary Key (primary, ER model): A candidate key that identifies the occurrence of each entity.
Primary Key (master health, relational model): A candidate key used in a table to identify the uniqueness of a record.
Privileges (permissions): Allows the user to perform actions on a given basic table and view.
Prototyping (prototype): a phase of the application lifecycle of a database, including the working model of the Gou database application.
Query-by-example (QBE): A non-procedural database language for relational DBMS. QBE is a graphical "dot-Press" method for querying the database.
The RDBMS: Relational DBMS.
The record: the same tuple (Tuple).
Recovery Control (Recovery controls): Pepsi, the process of restoring the database to the correct state.
rcursive relationship (Recursive relationship): a relationship in which a recursive relationship occurs when the same entity participates multiple times in different roles. For example, Staff supervises Staff.
Redundant data (redundant): Duplicate data stored in multiple tables.
Referential integrity (referential integrity): If an external health exists in a table, the external health value must match the value of the candidate key for some records in the primary table.
Relation (Relationship): A relationship is a table, it also has columns and rows.
Relational model: A data model that represents data in the form of a table (or relationship).
relational database (relational databases): A collection of normalized tables.
Relation (