A Database Administrator (DBA) is responsible for the performance, integrity, and security of a database. The role involves database design, implementation, maintenance, and repair. DBAs ensure databases are protected through backups, maintain data standards, optimize database performance, troubleshoot issues, and provide user access control. DBAs also periodically update systems and handle any migrations or upgrading of the database in response to new tools or needs .

Data abstraction in a DBMS is represented by three levels: the physical level, logical level, and view level. The physical level defines how data is stored physically in the database. The logical level describes what data is stored in the database and the relationships among those data, usually represented with ER diagrams. The view level is the highest level of data abstraction and presents only a part of the database relevant to a particular user, abstracting the complexities of the underlying data organization. This multi-layered approach allows different users to interact with the database conveniently without dealing with physical storage details .

ACID properties stand for Atomicity, Consistency, Isolation, and Durability, which ensure reliable processing of database transactions. Atomicity ensures that transactions are completed entirely or not at all. Consistency guarantees that a transaction takes the database from one valid state to another. Isolation keeps transactions separate until they're completed, preventing intermediate transactions from affecting other transactions, while Durability ensures that once a transaction is committed, it remains so even in the event of a failure. These properties are crucial for maintaining database integrity and consistency, especially in concurrent user environments .

A weak entity is an entity that cannot be uniquely identified by its own attributes alone and relies on a "strong" or "owner" entity. In a database model, a weak entity is represented with a dashed border in an entity-relationship diagram, and its existence depends on a strong relation identified via a foreign key. Additionally, a weak entity has a partial key, underlined with a dashed line, and participates in a relationship with a strong entity, ensuring referential integrity .

Static hashing maps search keys to fixed hash bucket addresses, leading to potential overflow issues as new records are added, hence requiring overflow buckets. Dynamic hashing adjusts the hash function as records increase, allowing the hash table to grow dynamically. It uses structures like extendible hashing, which split or merge pages, reducing overflow problems and offering better space utilization. Dynamic hashing is preferred in environments with frequent insertions, deletions, and updates due to its ability to adapt without compromising on performance and space .

COMMIT and ROLLBACK are SQL commands used to manage transactions. COMMIT saves all changes made during the transaction to the database, making them permanent and visible to other users. ROLLBACK, on the other hand, is used to undo changes made during the transaction, restoring the database to its previous state before the transaction began. These commands ensure the integrity and consistency of the database by allowing controlled commit and undo actions of transaction data .

The process of converting an ER-diagram into tables, known as Mapping, involves creating tables for each entity, converting relationships into tables or foreign keys, and defining attributes within tables. Each entity becomes a table, where entity attributes turn into columns. Relationships can require the creation of additional tables or foreign keys to link two entities directly, depending on their cardinals. This transformation helps in structuring the logical design based on the conceptual model outlined by the ER-diagram .

DBMS offers advantages over traditional file systems by providing data redundancy control, consistent data representation, efficient data accessibility, and improved data security. It ensures data integrity and enables concurrent data access by multiple users, while file systems typically lack these advanced features and require individual application handling of data redundancy and consistency issues .

Concurrency control is essential for maintaining database integrity in multi-user environments. It manages simultaneous execution of transactions to prevent conflicts when accessing shared data resources. By utilizing mechanisms like locking protocols and timestamp ordering, it ensures that transactions execute in a manner that is serializable, preventing phenomena like lost updates, temporary inconsistencies, or uncommitted data visibility, thus maintaining consistent state across database operations and users .

Normalization is a process to eliminate data redundancy and ensure data dependencies. The 1NF (First Normal Form) removes repeating groups by ensuring all attributes are atomic; for example, separate a column with multiple emails into individual columns. The 2NF (Second Normal Form) eliminates partial dependencies, ensuring all nonprime attributes are fully functionally dependent on the primary key, applied when a table with a composite key contains non-prime attributes only depending on a part of the key. Finally, 3NF (Third Normal Form) removes transitive dependencies, meaning non-key attributes should not depend on other non-key attributes—for instance, if a table includes employee ID, department name, and manager ID, and department name depends on manager ID, you must separate it .