Database and SQL

Outer joins are specifically designed to include rows that don't have matching values in the joined table. This includes LEFT JOIN (all from left table), RIGHT JOIN (all from right table), and FULL JOIN (all from both). Inner joins and equi-joins only return matching rows.

Both routines (stored procedures/functions) and triggers contain procedural code - SQL statements with control flow logic like IF/ELSE, loops, and variables. The key difference is invocation: routines must be called explicitly, while triggers execute automatically in response to events. Option A correctly identifies their shared characteristic.

A correlated subquery is one where the inner query references a value from the outer query, making it dependent on the outer query's results. The inner query is executed repeatedly for each row processed by the outer query. This is the opposite of a non-correlated subquery, which runs independently once.

SQL joins can theoretically involve any number of tables. While 2-table joins are most common (inner, left, right, full joins), you can join 3, 4, or more tables in a single query by chaining join conditions. The 'all of the above' option correctly captures that 1, 2, 3, or more tables are all possible.

Triggers are defined by an event (like INSERT), an optional condition (WHEN), and an action (procedural statement). They are created using SQL, execute for all applications connecting to the database, and can cascade by triggering other events, making other options incorrect.

When joining multiple tables, you generally need one join condition per pair of tables being joined to properly establish the relationship between them. For N tables, you typically need N-1 join conditions. Each condition connects two tables through matching keys. Without proper conditions, you risk a Cartesian product.

In Cognos Framework Manager, relationships and joins must be properly defined at the model level to ensure reports run correctly. Framework Manager creates the semantic layer that all reporting tools (Report Studio, Query Studio, Analysis Studio) depend on for accurate data retrieval and query generation.

When creating joins in Framework Manager, you must validate the model for loops (circular relationships that create infinite query paths) and fan traps (ambiguous many-to-one relationships through multiple paths). These structural issues cause incorrect query results or performance problems. Option A is wrong - cardinality can and should be specified. Option B is nonsense. Option D is incorrect - dimension tables can be joined.

Framework Manager allows importing metadata from multiple data sources into a single model, enabling reporting across heterogeneous databases and systems. This is a key feature for enterprise data warehousing where data comes from various sources. The model can combine tables from different databases, defining relationships and joins across data source boundaries.

The SAP table ZPP_PO_DATES is the standard custom table used for line hour calculations in production order processing. This table stores scheduling data needed for capacity planning and time calculations.

In Informatica PowerCenter, both Lookup and Stored Procedure transformations can be configured as unconnected (not connected to the pipeline, called via expressions). Since both lookup and stored procedure support this mode, selecting either one alone is incomplete, making 'both' the correct choice.

Constraint-based load ordering uses primary key and foreign key relationships to determine the correct sequence for loading data into multiple related tables. This ensures parent records are loaded before child records to maintain referential integrity. E-mail is unrelated to data loading, and target load plan is a different concept.

CREATE, ALTER, DROP, and TRUNCATE are DDL (Data Definition Language) commands that define or modify database structure. CREATE makes new objects, ALTER changes structure, DROP removes objects, and TRUNCATE empties a table while keeping its structure. These commands work on the schema, not the data itself.

INSERT, UPDATE, and DELETE are DML (Data Manipulation Language) commands that manipulate the actual data within database tables. INSERT adds new rows, UPDATE modifies existing data, and DELETE removes rows. These operations work on the data content, not the table structure.

SELECT is classified as DRL (Data Retrieval Language) or DQL (Data Query Language) - a category that specifically handles querying and retrieving data from databases. Unlike DML (which modifies data) or DDL (which modifies structure), SELECT only reads data without making any changes to the database.