Database Management Systems

Full buffering loads the entire table into memory. This is appropriate only for small static tables that are read frequently and rarely change, as the memory cost must be justified by high read activity. Transaction tables change too frequently, and internal tables are runtime structures.

A data element represents a semantic domain - it defines the business meaning and technical attributes of a field. It is not a physical definition (that's the domain level), not a business object (higher level), and not a technical domain (the underlying data type).

The OLE DB Command Transformation in SSIS data flow executes a SQL statement for each row, making it ideal for updating existing records row-by-row. Options A and B are destination components for inserting data, not updating. Option D is for type conversion, not database updates.

Tables, views, and stored procedures are all database objects within a DBMS. Flat files are external storage structures not part of the database schema, making C the correct choice as the odd one out.

MultiLoad DELETE mode is specifically designed to perform efficient delete operations on Teradata tables. Unlike standard SQL DELETE commands that process rows one at a time, MultiLoad DELETE mode can perform a global delete operation that spans all AMPs (Access Module Processors) simultaneously. It targets a single table for deletion, making it ideal for bulk data removal tasks. This statement accurately describes the DELETE mode functionality.

In Teradata utilities (FastExport, MultiLoad, TPump), the IMPORT command specifies the external client-side file that contains data values. These values are referenced by the USING clause for parameter substitution in the SELECT statement.

Oracle allows only one LONG column per table due to legacy design limitations (option A). VARCHAR2 minimum width is 1 character (option D) - you cannot create a VARCHAR2(0) column. CHAR values are blank-padded to the full defined width (option E) - this is a key difference from VARCHAR2. Option B is false: TIMESTAMP stores both date and time. Option C is false: BLOB stores binary data within the database, not in OS files (that would be BFILE).

MERGE statement (also called UPSERT) combines INSERT and UPDATE operations in one statement. It avoids writing separate UPDATE and INSERT statements for the same data. This increases performance (single pass over data, reduced overhead) and ease of use (one statement instead of multiple). MERGE is particularly useful in data warehousing for slowly changing dimensions, ETL processes, and synchronization scenarios where you need to update existing rows or insert new ones based on a match condition.

Oracle database transactions end in multiple ways. Explicitly with COMMIT (save changes) or ROLLBACK (discard changes). Implicitly when a DDL statement (CREATE, ALTER, DROP) or DCL statement (GRANT, REVOKE) executes - these auto-commit. Also when user exits the client tool (iSQL*Plus/SQL*Plus) or if the system crashes (forced rollback/commit). Any of these events terminate the current transaction.

The MERGE statement combines INSERT, UPDATE, and DELETE operations into a single statement, which avoids writing separate update statements. It is commonly used in data warehousing applications for ETL processes and can improve performance by reducing round trips to the database. The typo 'ncreases' in option B should be 'Increases'.

Database transactions end through multiple mechanisms: explicit COMMIT or ROLLBACK commands, implicit termination when a DDL (CREATE, ALTER, DROP) or DCL (GRANT, REVOKE) statement executes, or external events like user exit or system crash. All these scenarios can terminate a transaction, making 'Any one of the above' the correct answer.