Database Management Systems

For a table: BEFORE/AFTER (2) × statement/row (2) × INSERT/UPDATE/DELETE (3) = 12 triggers. INSTEAD OF triggers apply only to views, not tables.

In Oracle, a sequence's CURRVAL pseudocolumn cannot be used until NEXTVAL has been called at least once in the current session. Since the sequence was just created and NEXTVAL has not been called, attempting to select CURRVAL will raise an error: ORA-08002: sequence ABC.CURRVAL is not yet defined in this session.

Oracle databases have a limit of 1000 columns per table or view. This is a hard limit in the Oracle database architecture. Option A (900) is too low, while options C (1100) and D (1050) exceed the actual limit.

A category in business rule management systems is an identifier or tag that can be assigned to business rules for classification and organization purposes. It is not simply a set of identical conditions (option A) or just a property (option C). Categories help group and manage rules logically within a rule repository.

Database triggers are designed for centralized operations and ensuring related actions occur. They should not duplicate built-in constraints or other triggers. Option C describes enforcing related actions (e.g., audit logging on update). Option D describes global operations firing regardless of user.

Dbwrap refers to DB's Secured Applications Processing Environment (utilizing Citrix) as well as DB-Everywhere-Desktop in this internal corporate environment. Consequently, the option stating that both A and B are correct represents the accurate answer, whereas the other options are incomplete.

SIT (System Integration Testing) and UAT (User Acceptance Testing) environments in enterprise IT often involve shared support responsibilities between multiple vendors. TCS-DES (Tata Consultancy Services - Delivery Entity) partnering with Visionapp represents a common collaborative support model for database wrapping servers.

DBwrap production servers are maintained through a collaborative model where Visionapp coordinates with the TCS-DES team. This partnership ensures proper technical oversight and support for the production environment. Options suggesting independent operation by either party are incorrect, and DB Internals is not involved in this maintenance arrangement.

The dbwrap platform supports approximately 250 applications across the organization. This represents the scale of database services provided, including transaction processing, reporting, and data management for various business applications.

Dbwrap uses role-based access control (RBAC) where permissions are granted based on predefined roles rather than individual tasks or priorities. This model ensures consistent security governance and simplifies permission management across the platform.

Common dbwrap issues include both server/URL accessibility problems (network/connectivity issues) and registration problems with components like Appsense, OCX controls, and DLLs (client-side component registration). Both categories represent valid issue types that users encounter.

SQL execution follows these phases: Parse (syntax/semantic validation), Bind (variable binding), Execute (query execution), and Fetch (returning results to client). 'Retrieve' is not typically listed as a separate step in standard SQL execution phases.

Hard parse is more expensive than soft parse because hard parse involves optimization, query plan generation, and row source generation. Soft parse only checks the shared pool for an existing execution plan and skips these costly steps when a plan is found.

In OLTP (Online Transaction Processing) applications, individual SQL statements should execute very quickly - typically less than 10 milliseconds - to maintain high transaction throughput and responsiveness. Values of 50ms, 100ms, or 150ms would be considered too slow for OLTP workloads.

Using hints in SQL statements is generally not advisable because they hard-code optimization assumptions that may become outdated as data distribution changes. Hints should only be used as a last resort when the optimizer consistently makes poor choices and other tuning methods have been exhausted.