Database Management Systems

When determining which backups to use for restoration, SQL Server error log (A) contains backup and restore operation messages. The Windows Application Event Log (C) also records SQL Server backup events. The msdb.dbo.backupset table (D) stores complete backup history including timestamps, LSNs, and file paths. The msdb.dbo.sysbackuphistory table (B) doesn't exist - it's actually msdb.dbo.backupset and msdb.dbo.backupfile that contain this information.

When moving a database between servers while keeping reports functional, Backup/Restore (C) preserves all database objects, permissions, and metadata without users needing to modify anything. SMO (B) can also transfer databases with full metadata preservation. Detach/Attach (A) can work but is more disruptive and may require fixing orphaned users. Option D 'All' is incorrect because not all methods are equally suitable - Detach/Attach has significant limitations for this use case.

Among the operations listed, only Insert data (C) is allowed inside a trigger. Triggers execute in response to DML operations (INSERT, UPDATE, DELETE) and can themselves perform data modifications. CREATE INDEX, ALTER DATABASE, and RESTORE DATABASE are DDL operations that are not permitted within a trigger because triggers execute as part of the DML transaction and these DDL operations would break transactional integrity or require exclusive locks.

Oracle's DATETIME data types include TIMESTAMP (stores date and time), INTERVAL YEAR TO MONTH (for periods of years and months), and INTERVAL DAY TO SECOND (for periods of days, hours, minutes, seconds). Option B 'INTERVAL MONTH TO DAY' is not a valid interval type - intervals go from larger to smaller units. Option C 'TIMESTAMP WITH DATABASE TIMEZONE' is incorrect - the correct syntax is TIMESTAMP WITH DATABASE TIMEZONE or TIMESTAMP WITH TIMEZONE.

In XML DTD, ENTITIES are used to define storage units and reusable content. Entities allow you to define shortcuts for repeated text, special characters, or external content. ATTLIST defines attributes, ELEMENTS defines element structures, and DOCTYPE declares the DTD itself.

Drill-through reports in Cognos allow users to navigate from a summary report to a detailed report by clicking on data points, such as values in a chart. This is the primary purpose of drill-through functionality.

Rogers' Customer Profile Database (CPD2), which supports caller identification and business routing rules for their national IVR system, was historically developed and deployed on the Oracle 10g database engine to handle high-concurrency queries and ensure platform reliability.

IBM Cognos Framework Manager is a metadata modeling tool used to create and manage data models for Business Intelligence reports. It defines the relationships between data sources, creates calculated columns, and builds the semantic layer that Report Studio uses. It is not an ETL tool (those extract/transform/load data), not a database, and not a web portal.

Data Files - time series data in Asset Control is stored in data files rather than databases like Sybase or MS Access. The ac_bl files are for block data, not time series specifically.

DBMS_METADATA package can retrieve DDL (Data Definition Language) for all objects within a schema, making option A correct. It can also retrieve DDL for object grants on database tables, making option B correct. Options C and D describe reports that are not the primary function of DBMS_METADATA.

The Application Engine state record is a dedicated record that passes values between consecutive Actions within an AE program. It maintains state across the program execution, similar to how variables persist between steps. It does not store source code or application data - those are in other tables.

A two-tier connection in PeopleSoft 8 means connecting directly to the application server and database server. Running an upgrade or copy in Application Designer requires this direct database access mode, unlike regular operations that can use the three-tier (web server, application server, database) architecture.

The Application Engine state record is specifically designed to pass values between different actions within an AE program. It serves as a temporary storage mechanism for data that needs to be shared across multiple actions in a PeopleSoft AE program. It does not store source code (that's in the database) or application data (that's in application tables), and it's not used with the Process Scheduler.

A direct two-tier connection (client directly to the database) is required in PeopleSoft for administrative tasks performed in Application Designer, such as running database upgrades or copying projects. End-user activities like updating personal data, user profiles, or running queries typically go through a three-tier connection involving the application server.

Partition by Round Robin distributes records evenly across partitions by cycling through partitions sequentially - first record to partition 1, second to partition 2, and so on, then back to partition 1. This ensures balanced distribution regardless of data characteristics. Key partitioning causes skew if keys aren't uniformly distributed, Expression partitioning depends on the expression logic, and Range partitioning creates ordered but potentially uneven partitions.