Database Management Systems

Hibernate mapping files can define mappings for multiple classes/tables in a single .hbm.xml file. The root element can contain multiple elements, each mapping a different database table. This provides flexibility in organizing mappings - you can have one file per table or group related tables.

To switch the underlying database system, you must update the JDBC driver class, the connection URL, and the Hibernate SQL dialect to match the target database system. Therefore, all of these properties must be changed.

To map and connect to multiple databases in a single Hibernate application, you must configure and instantiate a separate `` for each database, as a single session factory is tied to one database configuration.

Hibernate supports both Native SQL queries and Hibernate Query Language (HQL, often mistyped as HSQL) for querying database records, giving developers flexibility to write database-independent or database-specific queries.

To commit a transaction in Hibernate, you must first retrieve the active transaction from the session and then call its commit method using session.getTransaction().commit(). The other options are syntactically incorrect or do not exist.

Hibernate fully supports bi-directional associations (such as one-to-many and many-to-one) between data models, allowing navigation from either side of the relationship. This is typically configured using the mappedBy attribute.

Oracle can use password files for authentication, but they are not mandatory disk components. Oracle can authenticate through operating system authentication, network authentication, or other methods without requiring password files.

The DUMP function in Oracle returns a VARCHAR2 value containing the datatype code, length in bytes, and internal representation of an expression - it's for debugging, not backup. Oracle backup is done using Data Pump (EXPDP/IMPDP) or older export/import utilities.

A DB config file in Ab Initio stores connection parameters (like DSN, username, password, connection details) required to connect to databases for reading or writing data.

The Source property of a database checkpoint contains the SQL query that retrieves data for comparison. This query defines which data to fetch from the database for checkpoint validation. The connection string is in ConnectionString property, and the number of rows or ID are not represented by Source.

In QTP/UFT Recovery Scenarios, the Trigger must be defined first as it specifies the event that activates the recovery scenario (e.g., a popup window appears or an application crash). Only after defining the trigger can you specify the recovery operations and other settings. The Recovery Scenario Name and Function definitions come after the trigger is established.

ADO (ActiveX Data Objects) uses Connection objects to establish database connectivity and Recordset objects to manipulate and query the returned data. These two objects form the foundation of ADO database operations - you first connect, then work with recordsets to read or modify data. Fields is a property of Recordset, Execute is a method, and Open/ConnectionString are properties/methods of Connection, not standalone objects.

ADO (ActiveX Data Objects) uses Connection objects to establish database connectivity and Recordset objects to manipulate and query the returned data. These two objects form the foundation of ADO database operations - you first connect, then work with recordsets to read or modify data. Fields is a property of Recordset, Execute is a method, and Open/ConnectionString are properties/methods of Connection, not standalone objects.

iSQL*Plus is a browser-based interface. Running it from a client PC requires an HTTP Server to serve the web pages and the iSQL*Plus Server application tier to process the database interactions.