Database and SQL

The key is to restore to a different database name (using the STOPAT option to specify time), then copy the missing table back. This avoids affecting the production database's availability while recovering the lost data.

In SQL, the DISTINCT keyword must appear immediately after the SELECT keyword and before the column list. This syntax is mandatory - DISTINCT cannot appear elsewhere in the SELECT clause. The keyword is part of the SELECT clause syntax, not a separate clause.

Option A correctly uses concatenation with || operator to combine columns and strings. Option C correctly concatenates string literals (quoted strings) - the column name 'ename' in quotes is a literal string, not a column reference, but this is valid SQL syntax. Options B and D have syntax errors.

Filters restrict result sets by applying conditions that narrow the data returned. Option B ('Filter occurrences') is vague and not a standard database concept. Option C is incorrect because while filters can reduce data volume, their primary purpose is data restriction, not performance enhancement - that's a side effect, not the function itself.

CREATE TABLE is a system privilege that allows a user to create tables in their schema. SELECT, EXECUTE (when on procedures), DELETE, and ALTER TABLE are object privileges that must be granted on specific database objects. System privileges are schema-wide authorities, while object privileges operate on named objects.

SQL provides built-in functions across multiple categories: character functions (SUBSTR, CONCAT, etc.), numeric functions (ABS, ROUND, etc.), date functions (SYSDATE, ADD_MONTHS, etc.), and conversion functions (TO_CHAR, TO_DATE, CAST, etc.). Option B correctly identifies character and numeric functions. Option E correctly identifies date and conversion functions. Option A is partially correct but incomplete. Options C, D, and F contain incorrect or non-standard category names.

The UNIQUE constraint allows null values (unless combined with NOT NULL). A UNIQUE index is automatically created for columns defined with PRIMARY KEY and UNIQUE constraints, making that statement correct, while NOT NULL ensures no nulls are allowed.

Subqueries can return zero, one, or multiple rows depending on context and operators used (B is true, disproving A). They can be nested beyond two levels in most databases (C is false). Subqueries can appear in various SQL statement types including DML and DDL, not just queries (D is false). They work with group functions (E is false). When using inequality operators with subqueries, single-row subqueries must be ensured or the ANY/ALL modifiers must be used (F is true, describing the inequality constraint requirement).

USER_CONS_COLUMNS displays the columns that participate in constraints defined on tables owned by the current user. USER_CONSTRAINTS shows constraint definitions but not column details. USER_OBJECTS lists all objects owned by the user. ALL_CONSTRAINTS includes constraints on accessible objects owned by others. USER_COLUMNS shows all table columns, not specifically constraint-related ones.

To grant all users query privileges, use GRANT select ON dept TO PUBLIC. PUBLIC is a reserved word that represents all database users. Option A incorrectly uses ALL_USERS which is not a valid grantee. Option B incorrectly uses ALL without PUBLIC. Option C incorrectly uses QUERY instead of SELECT and ALL_USERS. Option E incorrectly uses QUERY and incorrectly capitalizes PUBLIC.

The NOT NULL constraint can only be defined at the column level because it applies to a single column's values. Constraints like UNIQUE, CHECK, PRIMARY KEY, and FOREIGN KEY can be defined at either the column level or table level. Table-level constraints allow specification across multiple columns, which is essential for composite keys and multi-column conditions.

Outer joins preserve all rows from one or both tables, filling in NULLs where there are no matches. Use them when you need to keep unmatched rows (like finding customers with no orders) or when NULL values in join columns indicate non-matches rather than missing data. Inner joins only return matched rows, so outer joins are essential when unmatched data matters.

In version control systems, changes are propagated from one branch to another by performing a merge operation, which integrates the history and modifications.

To store values up to 9999999.999, you need 7 digits before the decimal point and 3 digits after, requiring a total precision of 10. Thus, DECIMAL(10,3) is the correct data type.