Database

Third Normal Form (3NF) requires that every non-key attribute must be functionally dependent on the primary key, and there should be no transitive dependencies. This means that all non-key attributes are directly determined by the primary key alone.

Network Model and Relational Model are both record-based logical models. Network Model uses graph structures with records and sets, while Relational Model uses tables (relations) with rows and columns. ER Model is not record-based but a conceptual modeling tool.

Data redundancy creates inconsistency because the same data stored in multiple places may be updated in one location but not others. This leads to different values for the same data entity, violating data consistency - a fundamental database principle.

In database systems, a domain is the set of all permitted values that an attribute can take. For example, a 'gender' domain might be {'M', 'F', 'Other'}, or an 'age' domain might be integers from 0 to 120. Domains define data type and constraints.

The DBA (Database Administrator) is responsible for the conceptual level of the DBMS, which defines the logical structure and relationships of data for the entire organization. End users interact with the external level, systems programmers work at the physical level, and clients are consumers of the database services.

Relations produced through an E-R model are always in 3NF (Third Normal Form) because the E-R modeling process eliminates transitive dependencies by design. The E-R approach maps entities and relationships directly to relations, ensuring that each relation represents a single entity or relationship.

A foreign key is an attribute (or set of attributes) in one table that references the primary key of another table, establishing a relationship between the two tables. This constraint enforces referential integrity between related tables in the database.

A subschema (or external schema) defines how a particular application or user views the data from the database. It provides a customized view of the database that is relevant to specific applications or user groups, hiding irrelevant details and restricting access to authorized data only.

Locking protocols prevent concurrent transaction problems: lost updates (overwriting uncommitted changes), uncommitted dependencies (reading dirty data), and inconsistent data (reading partially updated records). Locking ensures transaction isolation and serializability by controlling access to shared data items.

In an E-R (Entity-Relationship) diagram, an ellipsis (ellipse or oval shape) represents attributes of entity sets or relationship sets. Attributes describe the properties or characteristics of entities. Entity sets are typically represented by rectangles, and relationships by diamonds, while attributes are shown as ellipses connected to entities or relationships.

BCNF (Boyce-Codd Normal Form) is a stricter version of 3NF. If a relation is in BCNF, it automatically satisfies all requirements of 3NF, 2NF, and 1NF. BCNF eliminates all redundancy caused by functional dependencies, making it the highest practical normal form for most database designs.

The ER (Entity-Relationship) Model is an object-based logical data model because it represents real-world entities as objects with attributes and relationships between them. Unlike physical models, it focuses on logical structure. Unlike record-based models, it uses objects/entities rather than tabular structures.

File management systems suffer from all these problems: lack of data independence (programs depend on physical file structure), data redundancy (same data stored in multiple files), and update anomalies (changes must be made in multiple places leading to inconsistencies). DBMS was developed specifically to address these issues.

In the Relation Model, a column is referred to as an attribute, representing a specific property or characteristic of the entity. A row is called a tuple, the number of columns is the degree, and a relation represents the entire table structure containing tuples and attributes.

4th Dimension, FoxPro, and dbase-IV are all xBase database systems that support relational database features including SQL, relational operations, and tabular data structures. While they have xBase heritage, they are widely classified as relational databases in practice and support the core relational model concepts.

File updating refers to the ongoing process of maintaining files by periodically adding new records, changing existing records, and deleting obsolete records. This is a fundamental operation in file-based systems to ensure data remains current and accurate over time.

An index in database systems contains both the key values being indexed AND pointers/references to where those records exist in the main data storage. Without either component, the index would be non-functional.

In database theory, a domain defines the set of all permissible values that an attribute can take. This ensures data integrity by restricting values to valid types or ranges.

E-R modeling is a top-down approach because it starts with high-level entities and their relationships, then progressively refines the model into more detailed attributes and constraints.

A locked file can be accessed by only one user at a time to prevent concurrent modifications that could corrupt data or cause inconsistencies. Other users must wait for the lock to be released.

In database locking, shared locks are compatible with other shared locks. Multiple transactions can simultaneously hold shared locks on the same resource for reading purposes. Exclusive locks conflict with shared locks.

The DROP TABLE command permanently removes a table and its data from the database, along with any associated indexes, constraints, and dependencies. DELETE removes rows but keeps the table structure.

Relational database model characteristics include: Tables (relations) for data organization, Records (tuples) as individual data entries, and Complex Logical Relationships through foreign keys and joins. Tree-like structures characterize hierarchical models, not relational.

Both DELETE and REMOVE can remove rows from tables in various database systems. DELETE is standard SQL. TRUNCATE removes all rows but keeps table structure. The question is slightly ambiguous as 'remove' is not standard SQL.

The modify operation typically follows a look-up operation - you first locate/retrieve the record you want to change (look-up), then update its contents (modify). This sequence ensures you're modifying the correct data.

A report generator produces formatted output from database data, typically for printing reports. Option A is incorrect because report generators read data rather than update files. Option C refers to data entry which is a separate input function.

Report generators retrieve information from files AND answer queries to produce formatted output. Options A and C are incomplete - report generators do more than just store input or answer queries in isolation. Option D correctly combines both functions.

A database environment integrates data into shared databases rather than maintaining separate files. Users interact with the system, and DBAs manage it. Option B is correct because 'separate files' represents the old file-based approach that databases replace.

External level data hiding restricts what different users can see based on their access privileges. Director's salary hidden from employees is an example of view-level security. Conceptual and physical levels deal with logical structure and storage implementation, not user access control.

Embedded pointers stored within records create additional access paths to related data, serving as secondary indexes. Option A describes inverted indexes which are separate structures. Option C refers to primary keys, not embedded pointers.

A field (also called an attribute or column) is the smallest distinguishable unit of data in a record. Records consist of multiple fields, and files consist of multiple records. Option A is too general, while B refers to collections of records.

Record-based logical models represent data as records with fields. Network Model uses record structures with sets, and Relational Model uses tuples in relations. Object-Oriented Model organizes data as objects with methods, while E-R Model is a conceptual design tool, not a record-based implementation model.

A database schema is a comprehensive description of the database structure, including record types, data elements (fields), file structures, and relationships between records. Options A, B, and C each describe part of what a schema defines, making D the complete answer.

SQL (Structured Query Language) is the standard language used by virtually all relational DBMSs for data access and manipulation. 4GL and HLL are broader categories. While SQL is technically a query language, Option B is the specific, widely-adopted standard the question seeks.

Data hierarchy from lowest to highest: bit → byte → field → record → file → database. The database is at the highest level, integrating multiple files. A data bank is not a standard term in this hierarchy.

Data dictionaries contain metadata about the database: what data exists, where it's stored, who owns it, and how it's used. They do NOT contain information about physical storage devices like disk sizes - that's system-level information managed by the operating system, not database metadata.

Multimedia databases are specifically designed to store, manage, and retrieve various media types including full-text documents, images, audio clips, and video files. They handle the large storage requirements and metadata needs of diverse media formats, unlike traditional transaction databases that focus on structured text and numeric data.

A single telephone book entry containing a person's name and phone number represents a record in database terminology. The entire telephone book constitutes a file or database, while individual components like the name and phone number are fields. This analogy helps understand the data hierarchy: fields combine to form records, records combine to form files.

A transaction log maintains a complete chronological record of all modifications made to database contents, including inserts, updates, and deletions. This log is essential for database recovery after system failures, enabling rollback of incomplete transactions and forward recovery to restore the database to a consistent state. It also provides an audit trail for compliance and debugging.

Record management systems can be modeled after various physical record-keeping systems. Business forms (invoices, purchase orders), handwritten lists, and rolodex cards all represent valid models for organizing discrete records with structured fields. Each of these physical systems inspired the design of digital record management, emphasizing structured data capture and retrieval.

A master file contains permanent, relatively stable data that persists over time and serves as the primary reference for an organization's operations. Examples include customer master files, product inventory files, and employee records. Unlike temporary files (logs, updates), master files are perpetual and continuously updated with valid changes rather than being recreated periodically.

Record locking is a concurrency control mechanism that prevents conflicting simultaneous updates to the same database record. When one user acquires a lock on a record, other users must wait until the lock is released before they can modify that record. This prevents lost updates and ensures data integrity in multi-user database environments.

In relational database terminology, a table is organized as rows (also called tuples or records) and columns (also called attributes or fields). Each row represents a single complete entity or record, while each column represents a specific attribute or field that all records possess. This two-dimensional structure is the foundation of relational databases.