Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
hodb vocab
| Term | Definition |
|---|---|
| *Entity | Something that the database is concerned with, about which data can be stored. |
| *Primary key | This key uniquely identifies each row in the table. |
| *Statement of work | A document including the scope, objectives, and timelines for a given project. |
| Fixed width problems | Files where the length in characters of each column is the same. |
| *SQL | The language relational databases use to create their objects and to modify and retrieve data. |
| *Data integrity | Refers to the accuracy and the correctness of the data in the database. |
| *Relational database | A type of database that uses “relations,” tables, to store and relate tables. |
| *Statement of scope | A short statement of one or more paragraphs that says in clear, but general, terms what the project will do. |
| *Constraints | Limits on what the database will do. |
| *Redundancy | Refers to storing the same data in more than one place in the database. |
| *Attribute | Things that define aspects of entities. |
| Delimited files | These files have some sort of character separating columns of data. The delimiter is often a comma or tab, but can be any non-alphanumeric character. |
| *Foreign key | This key is the primary key repeated in another table to create a link between the tables. |
| Open-ended question | A question that has no set answer |
| Management Information Systems | A database optimized for queries that summarize transaction data |
| *Stakeholder | Anyone who has a stake in the process |
| Data warehouse | A collection of various types of business information |
| Transaction database | A database optimized for storing and processing real time transactions |
| *Requirement | Something the database needs to do to be successful |
| Report | A document for displaying summarized data |
| Business intelligence | A set of tools for analyzing business trends |
| Procedure | The official steps and rules for completing a process |
| XML | Marked up Unicode text that follows a few strict rules |
| Exception | An alternate way of doing a process |
| *Domain | The purpose or subject of a database |
| Cloud database | A database stored on internet servers |
| Close-ended question | A multiple choice question |
| Database service | A service that offers access to a cloud database to applications |
| Data mining | Combing data in a variety of formats for trends and patterns |
| Form | A document for gathering input |
| Work shadowing | Observing workers handling data on the job |
| User access | The permissions a user has to use or view database objects and data |
| *Client | Correct match: A program that requests a service |
| *Trigger | A program in SQL that is triggered by a database event. Executable scripts of SQL that are triggered by an event, such as insert, update, or delete. |
| *Natural key | A key based on one or more “natural” attributes of an entity |
| *Server | A program that offers a service to a requesting program |
| Actor | A person or program that makes some use of the database |
| Business rule | A rule about how data are acquired, stored, or processed |
| *Surrogate key | An artificial key, of just an incremented number |
| *Composite key | A key that consists of more than one attribute |
| Minimum cardinality | The smallest number permitted |
| *Weak entity | An entity that depends on another entity for its meaning |
| *Linking entity | An entity that resolves a many-to-many relationship into two one-to-many relationships |
| *Physical design | The design adapted to the RDMS and system constraints and features |
| *Entity relation diagram | One common method of depicting entities and relations in a diagram |
| *Domain entity | An entity that captures a chief element of the business problem |
| *Cardinality | Refers to the number of permitted records in a relational entity |
| *Lookup entity | Are used to store a set of values that can be looked up, such as state abbreviations or zip codes |
| Crow's feet notation | Notation for relationships that uses lines and circles to denote cardinality |
| *Logical design | The entity relation design without regard to what DBMS or system it will be on |
| Maximum cardinality | The highest number permitted |
| Naming conventions | A set of rules or suggestions that promote consistency in the naming of database objects |
| *First normal form | Removing repeated groups and arrays (making all data atomic) |
| Denormalization | The process of rejoining tables that were separated during the normalization process to improve performance |
| *Functional dependencies | Attributes that are related to each other rather than the key. They form subthemes within the entity. |
| *Update anomalies | Where the same data must be updated in several places |
| *Third normal form | Removes transient dependencies |
| *Transient dependencies | An attribute that depends on another attribute, not the key, for its meaning |
| *Second normal form | Removes functional dependencies |
| *Insertion anomalies | The inability to insert into data because other unknown data is required |
| *Normal forms | Rules for removing anomalies and redundancies |
| *Deletion anomalies | Where deleting some data inadvertently also removes other data |
Created by:
Argentum
Popular Computers sets