ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
GLOSSARY I Identifier: An attribute or column that helps to identify an entity or table instance; it is all or part of the entity’s or table’s primary key. Identifying Relationship: A type of relationship in which the parent entity contributes its primary key as part of the child entity’s primary key. Independent Entity Key: A type of entity in which no foreign keys participate in its primary key. Index: A database object used to enforce unique values in a table; an index can also be used to access table data more efficiently. Inheritance: The process of propagating foreign keys from parent entities to child entities based on relationship rules. Instance: A single occurrence or member of an entity. Integrity: A property of a data model in which all assertions hold. Integrity Constraint: A database feature that enforces foreign key relationships. Inversion Entry: An attribute or set of attributes that do not uniquely identify every instance of an entity, but which are frequently used for access. The database implementation of an inversion entry is a non unique index. Inverse Verb: A description of a relationship that conveys the business rule implied by the relationship. A verb phrase is read from the child entity to the parent entity like a sentence. IRD Rules: A business rule governing the treatment of Inserts, Replacements and Deletions of entity instances. K Key: A key is one or more columns that can be used to identify or access a particular row or set of rows. Keys can be created in a table, index, or referential constraint. A column can be part of more than one key. See also Composite Key and Unique Key. Key Area: The portion of the entity box that displays the primary key. This is the area above the line dividing the entity box. Key-Based Model: A data model in third normal form or higher. L Library: A piece of BASIC code that can be reused in different macros. Logical Design: The dimension of a data model that addresses real system requirements in the abstract, without consideration of data storage, performance or other physical implementation issues. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 412
GLOSSARY M Macro: Code written in the Sax BASIC language that can be used to retrieve or write information about objects. Materialized View: Materialized views are used to dynamically copy data between distributed databases. There are two types of materialized views: • Complex • Simple Complex materialized views copy part of a master table or data from more than one master table. Simple materialized views directly copy a single table. You cannot directly update the underlying data contained in materialized views. Metadata: All the information about a data warehouse that is not the actual stored data itself. Metadata describes the structure and relationship of data. Metamodel: A model about models. A metamodel describes the underlying structure of a model. Migration: The process by which a parent entity contributes foreign keys to a child entity. Model: Representation of the logical or physical design of a database. N Node: Diagram auto-layout term. Refers to a box on the model representing an entity or a view. Node Groups: A named subset of one or more database partitions. Non-Identifying Relationship: A type of relationship in which the primary key of the parent entity is inherited by the child entity as non-key attributes. Non-Key Attribute: An attribute that does not participate in an entity’s primary key. Non-Specific Relationship: A type of relationship that implies a many-to-many relationship between two entities. Because many-to-many relationships cannot be logically resolved, non-specific relationships are used for notational purposes and do not result in any foreign key migration. Normalization: The process of removing inaccurate, inconsistent, redundant and/or overly complex assertions in a data model. Not Null: The state of always having a value. Null: The state of having no value. O Object Type: An abstract data type or object composed of a collection of similar types of data. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 413
- Page 361 and 362: TUTORIALS > DOCUMENTING AN EXISTING
- Page 363 and 364: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 365 and 366: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 367 and 368: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 369 and 370: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 371 and 372: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 373 and 374: TUTORIALS > DIAGRAM NAVIGATION AND
- Page 375 and 376: TUTORIALS > DIAGRAM NAVIGATION AND
- Page 377 and 378: TUTORIALS > IMPORTING AND EXPORTING
- Page 379 and 380: TUTORIALS > IMPORTING AND EXPORTING
- Page 381 and 382: TUTORIALS > IMPORTING AND EXPORTING
- Page 383 and 384: TUTORIALS > DIMENSIONAL MODELING Si
- Page 385 and 386: TUTORIALS > DIMENSIONAL MODELING Wo
- Page 387 and 388: TUTORIALS > AUTOMATING TASKS Automa
- Page 389 and 390: TUTORIALS > AUTOMATING TASKS 7 Name
- Page 391 and 392: TUTORIALS > COLLABORATIVE MODELING
- Page 393 and 394: TUTORIALS > COLLABORATIVE MODELING
- Page 395 and 396: TUTORIALS > COLLABORATIVE MODELING
- Page 397 and 398: TUTORIALS > COLLABORATIVE MODELING
- Page 399 and 400: TUTORIALS > COLLABORATIVE MODELING
- Page 401 and 402: TUTORIALS > COLLABORATIVE MODELING
- Page 403 and 404: TUTORIALS > COLLABORATIVE MODELING
- Page 405 and 406: TUTORIALS > COLLABORATIVE MODELING
- Page 407 and 408: TUTORIALS > COLLABORATIVE MODELING
- Page 409 and 410: Glossary A Active File Directory: T
- Page 411: GLOSSARY Denormalization: The inten
- Page 415 and 416: GLOSSARY S Scale: The scale of a nu
- Page 417 and 418: Index Symbols 284, 299, 308 @var su
- Page 419 and 420: INDEX Metadata Import Options 44 Me
- Page 421: INDEX Adding a Macro 315 Deleting a
GLOSSARY<br />
I<br />
Identifier: An attribute or column that helps to identify an entity or table instance; it is all or part of the entity’s or<br />
table’s primary key.<br />
Identifying Relationship: A type of relationship in which the parent entity contributes its primary key as part of the<br />
child entity’s primary key.<br />
Independent Entity Key: A type of entity in which no foreign keys participate in its primary key.<br />
Index: A database object used to enforce unique values in a table; an index can also be used to access table data<br />
more efficiently.<br />
Inheritance: The process of propagating foreign keys from parent entities to child entities based on relationship<br />
rules.<br />
Instance: A single occurrence or member of an entity.<br />
Integrity: A property of a data model in which all assertions hold.<br />
Integrity Constraint: A database feature that enforces foreign key relationships.<br />
Inversion Entry: An attribute or set of attributes that do not uniquely identify every instance of an entity, but which<br />
are frequently used for access. The database implementation of an inversion entry is a non unique index.<br />
Inverse Verb: A description of a relationship that conveys the business rule implied by the relationship. A verb<br />
phrase is read from the child entity to the parent entity like a sentence.<br />
IRD Rules: A business rule governing the treatment of Inserts, Replacements and Deletions of entity instances.<br />
K<br />
Key: A key is one or more columns that can be used to identify or access a particular row or set of rows. Keys can be<br />
created in a table, index, or referential constraint. A column can be part of more than one key. See also Composite<br />
Key and Unique Key.<br />
Key Area: The portion of the entity box that displays the primary key. This is the area above the line dividing the<br />
entity box.<br />
Key-Based Model: A data model in third normal form or higher.<br />
L<br />
Library: A piece of BASIC code that can be reused in different macros.<br />
Logical Design: The dimension of a data model that addresses real system requirements in the abstract, without<br />
consideration of data storage, performance or other physical implementation issues.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 412