Term
|
Definition
| Collection of persistent data that can be shared and interrelated |
|
|
Term
|
Definition
| Data resides on stable storage such as a magnetic disk and is kept until the data is no longer relevant |
|
|
Term
|
Definition
| Database can have multiple uses and users |
|
|
Term
|
Definition
| Data stored as separate units can be connected to provide a whole picture |
|
|
Term
|
Definition
| Cluster of data usually about a single subject can be accessed together; can denote a person, place, thing, or event |
|
|
Term
| Database Management System |
|
Definition
| Collection of components that support data acquisition, dissemination, maintenance, retrieval, and formatting |
|
|
Term
|
Definition
| Language and graphical tools to define entities, relationships, integrity constraints, and authorization rights |
|
|
Term
|
Definition
| Control mechanisms to prevent interference from simultaneous users and recover lost data after a failure |
|
|
Term
|
Definition
| Language and graphical tools to access data without complicated coding |
|
|
Term
|
Definition
| Graphical tools to develop menus, data entry forms, and reports; data requirements for forms and reports are specified using nonprocedural access |
|
|
Term
| Procedural Language Interface |
|
Definition
| Language that combines nonprocedural access with full capabilities of a programming language |
|
|
Term
|
Definition
| Control mechanisms to prevent interference from simultaneous users and recover lost data after a failure |
|
|
Term
|
Definition
| Tools to monitor and improve database performance |
|
|
Term
|
Definition
| Named, 2-D arrangement of data; consists of a heading part and a body part; store collections of entities |
|
|
Term
|
Definition
| An industry standard language supported by most DBMSs that includes statements for database definition, database manipulation, and database control; can be used to define tables, relationships among tables, integrity constraints, and authorization rights |
|
|
Term
|
Definition
| Allows a user to define properties of columns, such as the data type and field size |
|
|
Term
|
Definition
| Request for data to answer a question |
|
|
Term
| Nonprocedural Database Language |
|
Definition
| Language such as SQL that allows you to specify the parts of a database to access rather than to code a complex procedure; does not include looping statements |
|
|
Term
|
Definition
| Convenient tool to enter and edit data |
|
|
Term
|
Definition
| Enhance the appearance of data that is displayed or printed |
|
|
Term
| Procedural Language Interface |
|
Definition
| A method to combine a nonprocedural language such as SQL with a programming language such as Java or Visual Basic; adds the full capabilities of a computer programming language |
|
|
Term
|
Definition
| Unit of work that should be processed reliably without interference from other users and without loss of data due to failures |
|
|
Term
|
Definition
| Reliable and efficient processing of large volumes of repetitive work. DBMSs ensure that simultaneous users do not interfere with each other and that failures do not cause lost work |
|
|
Term
|
Definition
| DBMSs that support large databases with many simultaneous users |
|
|
Term
|
Definition
| Run on personal computers and small servers and support limited transaction processing features but have a much lower cost; support databases used by work teams and small businesses |
|
|
Term
|
Definition
| Emerging category of database software; resides in a larger system, either an application or a device such as a PDA or a smart card; provide limited transaction processing features but have low memory, processing, and storage requirements |
|
|
Term
|
Definition
| Extends the features available with the database software; in some cases, it competes directly with the database product |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Database technology that supported sequential and random searching, but the user was required to write a computer program to obtain access; usually regarded as file processing systems rather than DBMSs because they did not offer much support for relating data (file processing systems can manage only one entity, whereas a DBMS can manage many entities and relationships); 1960s |
|
|
Term
|
Definition
| first true DBMSs as they could manage multiple entity types and relationships; to obtain access to data, a computer program still had to be written; "navigational" because the programmer had to write code to navigate among a network of linked records; 1070s |
|
|
Term
| Committee on Data Systems Language (CODASYL) |
|
Definition
| Standards organization (only had limited market acceptance partly because IBM supported the hierarchical data model instead |
|
|
Term
|
Definition
| Known as relational DBMSs because of the foundation based on mathematical relations and associated operators; optimization technology was developed to make nonprocedural access efficient; transaction processing; 1980s |
|
|
Term
|
Definition
| DBMS that includes multi-media, active, distributed processing, more powerful operators, data warehouse processing, XML enabled; "object-relational" because these DBMSs view any kind of data as an object to manage; 1990s to 2000s |
|
|
Term
|
Definition
| Database should have an identity separate from the applications (computer programs, forms, and reports) that use it |
|
|
Term
|
Definition
|
|
Term
|
Definition
| User level; each user can have a separate view of a database tailored to the group's specific needs |
|
|
Term
| Three Schema Architecture |
|
Definition
| An architecture for compartmentalizing database descriptions; proposed as a way to achieve data independence |
|
|
Term
|
Definition
| Defines the entities and relationships; represents the logical meaning of the database; only one of these can exist |
|
|
Term
|
Definition
| Represents the storage view of the database; defines files, collections of data on a storage device such as a hard disk; can only be one of these |
|
|
Term
|
Definition
| Describe how a schema at a higher level is derived from a schema at a lower level |
|
|
Term
|
Definition
| Allows geographically dispersed computers to cooperate when providing data access |
|
|
Term
|
Definition
| Program that submits requests to a server |
|
|
Term
|
Definition
| Processes requests on behalf of a client |
|
|
Term
| Client-Server Architectures |
|
Definition
| An arrangement of components (clients and servers) among computers connected by a network; supports efficient processing of messages (requests for service) between clients and servers) |
|
|
Term
|
Definition
| Each processor has its own memory but processors share the disks |
|
|
Term
| Shared Nothing Architecture |
|
Definition
| Each processor has its own memory and disks |
|
|
Term
|
Definition
| a DBMS capable of utilizing tightly-coupled computing resources (processors, disks, and memory). Tight coupling is achieved by networks with data exchange time comparable to the time of the data exchange with a disk; promises performance improvements and high availability |
|
|
Term
|
Definition
| A database in which parts are located at different network sites; this technology supports local control of data, data sharing for requests involving data from more than one site, and reduced communication overhead |
|
|
Term
|
Definition
| Given a report or some data from a database |
|
|
Term
|
Definition
| Requests existing forms or reports using parameters, input values that change from usage to usage; ex.: may indicate a date range, sales territory, or department name |
|
|
Term
|
Definition
| Most active user; skilled enough to build a form or report when needed; have a good understanding of nonprocedural access; this is when ad hoc or unplanned usage of a database is necessary |
|
|
Term
|
Definition
| Responsible for collecting requirements, designing applications, and implementing information systems; create and use external views to develop forms, reports, and other parts of an information system |
|
|
Term
|
Definition
| A support position that specializes in managing individual databases and DBMSs; assist both information systems professionals and functional users; have a variety of both technical and non-technical responsibilities; primary technical responsibility is database design |
|
|
Term
| Information Resource Management |
|
Definition
| Goal is to use information technology as a tool for processing, distributing, and integrating information throughout an organization |
|
|
Term
|
Definition
| A management position that performs planning and policy setting for the information resources of an entire organization |
|
|
