Database Management Systems

To switch the underlying database in a Hibernate application, you must update the driver class, the connection URL, and the SQL dialect property to match the target database system. Thus, all of the above properties must be changed.

Hibernate supports multiple query approaches: Native SQL (direct database queries) and HQL (Hibernate Query Language, an object-oriented query language). Both can be used depending on the use case, giving developers flexibility in how they query data.

Changing the underlying database system requires updating multiple properties: the driver class (connection.driver_class) to load the correct JDBC driver, the connection URL (connection.url) to point to the new database, and the dialect property to use the appropriate SQL dialect for optimal performance.

For caching historical library information retrieved from a database, using the Cache object provides the best performance. The Cache object allows explicit control over what data is cached, duration, and expiration policies. Output cache is for entire page responses, ASP.NET central cache is not a standard term, and client cache relies on browser caching which is less reliable for server-fetched data.

Database stored procedures, triggers, and views are typically stored in the database dictionary as both the original source code (for viewing/editing) and in a compiled/p-code form (for execution efficiency).

The question asks which statement does NOT correctly define the JDBC-ODBC difference. Option A claims 'ODBC can be directly used with Java' which is FALSE - ODBC cannot be directly used with Java because it uses a C interface. This makes A the incorrect statement, which is what the question seeks. Options B, C, D correctly describe real differences (pointers removed from Java, vendor origins, manual vs automatic installation).

SQL Server 2005 Notification Services was designed for sending personalized messages to large groups. Database Mirroring is for high availability, and Integration Services is for ETL/data transformation.

When upgrading from SQL Server 7.0 Standard Edition SP4, you can only upgrade to SQL Server 2005 Standard Edition. You cannot directly upgrade to Developer, Express, or Enterprise editions from a Standard edition base.

The correct tool for running T-SQL queries from command prompt in SQL Server 2005 is sqlcmd, which is not listed among the options. DTUTIL is used for SSIS package utilities, BCP is for bulk data copy operations, and Object Explorer is a GUI component in SQL Server Management Studio.

SQL Server 2005 supports three recovery models: Simple (minimal logging, auto-log truncation), Full (complete transaction logging, point-in-time recovery), and Bulk Logged (minimal logging for bulk operations). Since all three listed options are valid recovery models, 'All of the above' is correct.

Full Text Search in SQL Server 2005 provides specialized indexing and querying capabilities for text data stored in character columns. It enables fast linguistic searches for words and phrases, supporting features like stemming, thesaurus lookups, and proximity searches. Option B describes Service Broker and option C describes Database Mail, both unrelated features.

In WebSphere ESB, the message logger primitive stores messages in the Common Database (WPRCSDB). The other databases serve different purposes: MEDB for the messaging engine, SIDB for service integration bus configuration, and BPEDB for business process choreographer data.

When database administrators restrict table creation permissions, the bpeconfig.jacl script with -createDB option set to 'no' will generate the createSchema.sql script. This script can be given to DBAs to execute tables creation under their authority, maintaining security while ensuring proper schema setup.