Database and SQL

In PeopleSoft, PSDBFIELD is the system catalog table that stores the definitions of all fields used to create page controls and database columns.

PeopleSoft Application definitions (records, pages, menus, etc.) are stored in PeopleTools tables, which are system tables that store metadata about application objects. Application Tables store actual business data, and System Catalog is a database-specific concept.

Application data is cached on the Application server to improve performance. This cache reduces database hits by storing frequently accessed data in memory. Web servers handle HTTP requests, and Batch servers process background jobs.

The Reasonable Date property validates that dates are within an acceptable range (like not more than 30 days from current date). It prevents users from entering unrealistic dates. Required, Default, and Constant settings don't perform this date range validation.

PeopleSoft uses the prefix 'PS' followed directly by the record name (e.g., PSRECORDNAME) for its internal system tables, distinguishing them from application tables which use 'PS_'.

Selecting the 'Search Edit' property on a PeopleSoft record field forces the system to validate the data entered in that field when the search dialog is saved or executed.

Cursors are not part of core SQL - they are part of procedural SQL extensions like PL/SQL (Oracle) or T-SQL (Microsoft). COMMIT, SAVEPOINT, and TRUNCATE are all standard SQL commands for transaction control and data definition respectively.

The INTERSECT operator in SQL automatically sorts the final result set to eliminate duplicates and find common rows. UNION ALL, DISTINCT, and UNIQUE do not inherently guarantee sorted order.

Set operations UNION, INTERSECT, and MINUS (or EXCEPT) all have equal precedence in SQL. They are evaluated left to right when chained together. None of them has higher priority than the others, making 'None of above' the correct answer.

In standard SQL, a subquery cannot have an ORDER BY clause when used in contexts where a set operation is expected (like WHERE, HAVING, or as a derived table). The ORDER BY would only apply to the outer query. However, this is context-dependent - some modern SQL implementations allow ORDER BY in subqueries with LIMIT/OFFSET.

All three operations end a user transaction. COMMIT explicitly ends the transaction by saving changes. DROP and TRUNCATE are DDL operations that implicitly commit the current transaction and start a new one in most databases (Oracle, PostgreSQL). Therefore 'All of above' is correct.

Unique key constraints require an index to enforce uniqueness efficiently. NOT NULL constraints and CHECK constraints do not require indexes - they're validation rules. Therefore, only unique keys (C) mandatorily require an index.

Modern databases support multiple procedural languages. SQL runs natively. PL/SQL (Oracle's procedural extension) runs within Oracle databases. Java can run inside databases via Java Stored Procedures (Oracle JVM, SQL Server CLR, etc.). So all three (D) are correct.

SQL is a set-oriented language because it operates on entire sets of data (relations) at once, rather than processing individual records or tuples one by one like procedural languages.