Database Management Systems

The ReceiveTimeout property controls session lifetime in WCF - if no message is received within this timeout period, the session is considered closed and the channel faults. Unlike SendTimeout (outgoing) or OpenTimeout (connection establishment), this specifically governs incoming message tolerance.

Informatica PowerCenter, IBM DataStage, and Ab Initio are all enterprise-grade ETL tools used for data integration and transformation. Each provides visual designers, transformation libraries, and connectivity to diverse data sources.

Data warehouses are specifically designed to store and analyze historical data over time, unlike operational databases that handle current transaction processing. This temporal dimension enables trend analysis, reporting, and business intelligence.

An ETL mapping includes source definitions (where data comes from), target definitions (where data goes), and transformations (how data is modified in between). All three components are essential parts of a complete data flow. None of these alone constitute a complete mapping.

A data warehouse is a specialized database designed for query and analysis rather than transaction processing. It consolidates data from multiple sources into a single repository optimized for reporting and analytics. While it uses database technology, 'database' is the most accurate answer among the options given.

A data mart is a targeted, subject-oriented subset of a data warehouse designed to serve a specific business line, department, or user group. It is not a variable, making the other options incorrect.

Datamarts are typically classified into two main types: Independent datamarts (created directly from operational systems without a data warehouse) and Dependent datamarts (created from a central data warehouse). Some sources mention a third type (Hybrid), but the standard answer in most ETL/data warehousing contexts is 2 types.

Data warehouses are specifically designed to store historical data for long-term trend analysis and decision-making. They are optimized for read-heavy analytical queries, not the frequent read-write operations of operational databases. Operational data is stored in OLTP systems, while data warehouses archive the historical snapshots.

Data warehouses use denormalized schemas (star and snowflake schemas) which reduce the number of joins needed for queries. They also create numerous indexes to optimize query performance on large datasets. Both fewer joins and more indexes are key architectural advantages that enable fast analytical queries.

SCD Type 1 (Slowly Changing Dimension) overwrites old data with new data, storing only the current state of the record. No history is maintained - when a value changes, it is simply replaced. This is the simplest SCD method and is appropriate when historical tracking is not needed.

SCD Type 2 maintains both current and historical data by creating new rows for each change, preserving the complete history of changes. Unlike Type 1 which only keeps current data, Type 2 tracks every version of a record with effective dates or version numbers. This allows historical analysis of how values changed over time.

Oracle, as an operational database (OLTP system), is designed to store and manage current operational data for day-to-day business transactions. While it can be configured for various purposes, its primary use is for operational data rather than historical analysis (which is typically handled by data warehouses). Historical data storage requires different design approaches.

Oracle is a relational database management system (RDBMS), not a programming language. Oracle Corporation provides the Oracle Database software, and while it includes PL/SQL as a procedural extension, 'Oracle' itself refers to the database platform. Option A incorrectly classifies Oracle as a programming language.